On Wed, May 19, 2021 at 02:15:29PM -0400, Polyna-Maude Racicot-Summerside wrote: > Why would a package I get from a git repository be supportable but a > package I save some packaging time and get from another source (Kali, > Ubuntu for example) would become unsupportable ?
Because things you pull from git and install in /opt or /usr/local or even $HOME do not interfere with the Debian system. They don't create dependency issues within the dpkg database, nor do they overwrite essential system libraries or files, nor do they cause removal of Debian packages, etc. An Ubuntu or Kali package, especially a badly built one, can cause *all* kinds of havoc. Even some third-party repositories set up by Debian developers have been notorious for causing these kinds of problems in the past -- take a look at the history of the "debian multimedia" package repositories, in particular. > So you are telling me that support stop as soon I build myself a custom > package but if I build software and put it outside the packaging system, > it's supportable ? It's not quite that cut-and-dried, but basically: yes. Packages have a much bigger potential for breaking your system. > And if I build myself a package, for example I packaged all my roms used > for gaming into a deb file, this way it's easy to install and I use a > repository on my local network. By doing it this way, my gf who already > does her updates can also update the pack of roms I got. > So this is bad and make me loose community support ? This is OK if you're competent to do it correctly. But this is a specialized task, which the generic #debian channel may not be equipped to help you with. We can point you toward beginner tutorials. For help with any problems you encounter while building your own local packages, there are some channels on the OFTC network: #packaging and possibly #debian-mentors, although the latter is really for packages that are intended to become part of Debian, not personal/local projects.
