deloptes <delop...@gmail.com> writes:

> Anssi Saari wrote:
>
>> Never mind, old libmtp in /usr/local was the problem. Note to self,
>> these should be cleaned up sometimes...
>
> One good advise is to isolate custom builds and follow the rule
> 1. if possible build debian package

That doesn't do much by itself.

> 2. if not possible isolate in dedicated "prefix" for example /opt/clementine
>         in this case create a startup script with PATH and LD_LIBRARY_PATH

Possible. I've gotten into the habit of installing self built stuff
under /usr/local and non-free binaries under /opt. Or actually I put my
huge library of two AppImages under /opt too. I've thought about
installing "environment modules" since that's what we use at work to
manage what version of what software is in $PATH etc. Looks like it's
even packaged for Debian as environment-modules. But kind of overkill
for my purposes and we have people to maintain that at work so it's not
like I'm familiar with it.

> 3. keep track of such customizations

As I only have two places to check so keeping track isn't a
problem. Remembering to remove old stuff is, even Debian
packages. Trying to figure out this problem I removed over 100 packages
that were from oldstable (i.e. Stretch) and no longer in Buster. Mostly
libs that had no dependencies to anything so probably stuff that was
really old.

Reply via email to