-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Oct 13, 2017 at 12:56:36PM +0100, Jonathan Dowland wrote: > On Fri, Oct 06, 2017 at 03:43:20PM +0200, to...@tuxteam.de wrote: > >(And while we're painting the shed, I'd go for a /usr/bin/im.d, with a > >dispatcher script in /usr/bin/im or something...) > > Software Collections https://www.softwarecollections.org have a pretty > robust way of managing this sort of thing.
Well, yes. But that would be painting the shed with an aircraft carrier ;-) FWIW, if going that far, I'd rather prefer Gnu Guix [1] which also manages the repeatable build of specific software versions. But back on topic, I think in the current case (old, well established binaries from X or ImageMagick) it just makes sense to live with the inconsistencies (and keep the lessons for when we go for a new system). Many younger generation (collections of) binaries (ip, openssl, git) tend to do the right thing anyway. Cheers [1] https://savannah.gnu.org/projects/guix/ - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlngsdoACgkQBcgs9XrR2kafcgCeLKEq+75ai9WLSzQx7FFW0VbU njEAn1atZdXY7fjex8Z3vWmoswTJVVQ3 =Gi5S -----END PGP SIGNATURE-----
