On Sat, 14 Sep 2013 00:34:07 -0700 "H. S. Teoh" <hst...@quickfur.ath.cx> wrote: > > When I custom-install stuff, I usually put it in /usr/local/*, or even > give it a dedicated home in /home (though usually just > /usr/src/$pkgname/install or some such), away from the package manager > managed stuff. It tends to work far better that way. Fighting with > the package manager never ends well, as does installing external > files into directories managed by the package manager.
My understanding (purely from the link below) was that /usr/local/* was *specifically* for non-package-managered stuff, whereas /usr/* was *specifically* for package-managered things: http://unix.stackexchange.com/questions/8656/usr-bin-vs-usr-local-bin-on-linux > If I have to install libraries not in the apt repository (or multiple > conflicting versions of the same library), I tend to put it either > under an entirely different PREFIX, preferably under a dedicated > subtree for the app I'm trying to build I had no idea you could do that! That's fantastic: despite my migration towards Linux, I had been worrying about the day I'd inevitable have to deal with multiple versions of the same thing. > > Hence my first comment: I prefer to just grab the Windows version > > and run it in wine. That usually just works. > > I dunno, wine doesn't seem to like my GUI configuration (or lack > thereof :-P). It just falters in its steps and gasps every now and > then, that I don't trust that whatever program it's running is > actually doing what it should be doing. I still rather build from > source. > I find GUI apps to be butt-ugly under wine ;) But often usable otherwise (not that I've used it much so far).
