Patrick Shanahan wrote: > * J Sloan <[EMAIL PROTECTED]> [01-15-07 15:16]: > [...] >> While this is technically true, the fact is that any official suse >> rpm packages install binaries in /usr/bin, /usr/sbin, etc. OTOH, >> tarball builds inevitably default to installing binaries in >> /usr/local/bin, /usr/local/sbin, etc, so there is no collision. >> According to old unix traditions, /usr/local is where non-vendor >> stuff is installed. > > But you only address a very small segment. You do not consider the > libraries, configuration files, and maintaining the rpm database. The > statement I made is very solid.
Actually I do consider: the libraries -> /usr/local/lib the config files -> /usr/local/etc But the rpm database is not a factor here since this is all outside the scope of the rpm database. Unlike windoze with the registry, Linux will still run and function even if the rpm database is nuked, but I agree that it's best to maintain its integrity, for manageability purposes. I try to always use rpms, or to build them from the source whenever practical, but in some cases, it's quickest to just allow a self compiled app to live in /usr/local. Joe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
