-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Douglas Allan Tutty wrote:
> On Tue, May 01, 2007 at 10:12:14PM +0200, Joe Hart wrote:
[snip]
>>> Shouldn't pre-compiled tarballs go in /opt?
>>
>> Does it really make a difference? What matters is that it is in a
>> different place than /bin or /usr/bin so that the system won't clobber
>> it when it gets upgraded. Perhaps I am wrong. Personally, I have some
>> things in /opt and some others in /usr/local/bin.
>
> I suppose it makes a difference depending on how update tarballs get
> handled. If you just get a new tarball, how do you ensure that all the
> old stuff is removed? With everything under /opt then you just remove
> the directory.
>
> If you're compiling, then a make uninstall (or whatever) handles this.
Some people put them in /home/username so that only they have permission
to use them, and others put them in /opt and yet others in /usr/bin.
IMO, it doesn't really matter as long as one knows what is where, but
you are definitely right in saying that if they are in one place it
would be easier to keep track of them.
Joe
- --
Registerd Linux user #443289 at http://counter.li.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGOOWViXBCVWpc5J4RAipUAJ4nzijPjBXWoH5ba4XoanW3ggmyGwCgwtY+
Ne8z9sGBVCYlJ9j4YFkZpnE=
=LEks
-----END PGP SIGNATURE-----