Ask a vague nonspecific question, get a vague nonspecific answer. Add some "approved" this,"official" that and "windows" the other thing, get a snarky vague nonspecific answer.
GNU/Linux is not Windows, and most distributions are run by volunteers. There is no "approval", only guidelines and suggestions. You are free to do whatever you like, install whatever you like, and take responsibility for any mess you make in the process.
Your block of copy-paste from some "how to use apt instead of apt-get" type post above isn't a useful question, so I'm not sure how you expect a useful answer.
You might as well ask "Can I use a <copy-pasted list of types of spoon> to trap giraffes", because you'll get the same kind of answer... Especially if you don't specify what species of giraffe you are after or what kind of trap you are trying to build.
If software is not in the debian repositories it's not because it isn't "approved" it's because nobody has volunteered to maintain testing and packaging for it. That might be because it's non-free, low quality, or difficult to compile, or it might be because there's simply not much interest in it.
If you want something that isn't in the repositories, then it's up to you to figure out how to install it. Best practices (mostly warnings regarding what not to do if you don't want it to interfere with debian package management) are provided in the wiki page I linked above.
How exactly you go about installing something from a non-repository source will vary from one project to the next depending on what it contains and which build system it uses, and will often entail compiling from source code.
Note that generally means reading and understanding instructions...
GNU/Linux is not Windows, and most distributions are run by volunteers. There is no "approval", only guidelines and suggestions. You are free to do whatever you like, install whatever you like, and take responsibility for any mess you make in the process.
Your block of copy-paste from some "how to use apt instead of apt-get" type post above isn't a useful question, so I'm not sure how you expect a useful answer.
You might as well ask "Can I use a <copy-pasted list of types of spoon> to trap giraffes", because you'll get the same kind of answer... Especially if you don't specify what species of giraffe you are after or what kind of trap you are trying to build.
If software is not in the debian repositories it's not because it isn't "approved" it's because nobody has volunteered to maintain testing and packaging for it. That might be because it's non-free, low quality, or difficult to compile, or it might be because there's simply not much interest in it.
If you want something that isn't in the repositories, then it's up to you to figure out how to install it. Best practices (mostly warnings regarding what not to do if you don't want it to interfere with debian package management) are provided in the wiki page I linked above.
How exactly you go about installing something from a non-repository source will vary from one project to the next depending on what it contains and which build system it uses, and will often entail compiling from source code.
Note that generally means reading and understanding instructions...
for example is not what the README at the radioactive github page says about installing, and is missing the rather important step of unpacking the archive or cloning the project. You only need to install git if you intend to do the latter.
Statistics: Posted by steve_v — 2024-07-09 06:09