News for hackers. Stuff that matters.
Re:Using /usr/local by pfaux on Thursday March 26, 2009 @05:25PM (#534194)
Yes, essentially I follow the same simple system. But to avoid adding each bin directory to the path, I create for each application an executable script in /usr/local/bin that performs an "exec /opt/package/bin/app-name $@". The only directory to add to the path is /usr/local/bin. Then, as you say, managing multiple application versions is as easy as repointing the symlink in /opt.

No need for package managers that do who knows what to your system.

The one exception is for shared libraries, which I build to /usr/local. That way 'make' can find them easily without fiddling with LDPATH.

Re:Using /usr/local by donw on Thursday March 26, 2009 @07:51PM (#534362)
Why not just do symlinks in /usr/local/bin?
Re:Using /usr/local by pfaux on Friday March 27, 2009 @03:16AM (#534799)
A script can pass specific environment variables to the particular instance of the application.