Quote:
Originally posted by wmcase
1) Where and how to create a specific downloads directory with specific program sub-directories i.e. is /downloads with chown root, chgrp user1 (me), chmod 775 a good idea? Does that give me enough latitude or is it too permissive. I have a two computer home network used mainly by me.
|
I have ~/src, chmod 700, with categories - editors, net, blah - and apps - vim, nedit, blah - inside those. Tarballs inside those.
Quote:
2) When I unzip program.tar.gz or program.tar.bzip2 should I create the tar archive in /downloads/program/archive or should I archive elsewhere? Don't some people use /tmp for archives and is this a good pracitice?
|
I create the untarred directory right next to the tarball. Name the last one foo.bak. If everything goes well, I delete the old and keep the new.
Quote:
3) After building from an archive to a /usr/share/program directory should I remove the archive directory because its taking up space and is un-neat (space is not a problem at the moment). Or, is it somehow safer to leave the archive in place?
|
I keep the new because I might want to check out the source, look over the config logs, change a flag and recompile, whatever. I install everything possible to /usr/local or, failing that, ~/bin or, failing that, then to /usr. Unless it's a lib that I think is easier pathwise to just stick in a default place. All the downloading and compiling is as regular user - I just su or switch to a virtual console as root to install.
That's just me. I'm sure there's a zillion ways and it probably depends on the setup, users, etc. I'm the only user of my machines (I hope
) so I do things however I like.