You are not logged in.
I have gotten very used to adding the paths of my executables to my .bashrc (and then linked by .profile). But does #! like to install things to /lib or /lib64 or /usr/bin or something so I don't have to do this? I remember writing a script to automatically add the path for where ever I installed a file, but was wondering if this can be bypassed by installing my programs to the "right" directory. I am not what I would call novice to linux, but definitely can improve. Always
Thanks.
Coffee and Meat
Offline
I realize maybe this is in the wrong section. I apologize and if a moderator wishes to move this to the right topic please do so!
Thanks and sorry I will get used to the forums!
Coffee and Meat
Offline
Most programs will install to a folder in your $PATH, an environment variable equal to all of the folders you can run programs from without typing out the full path name. To see all of the folders in your $PATH, type
echo $PATHto find out where a specific executable resides, like terminator for example, enter
whereis terminatormost programs install to /usr/bin or somewhere else in your /usr folder.
Offline
Ok right. So I already added /usr/bin to my PATH but doesn't whereis only work within that PATH variable? Otherwise I would just use find command. I am just asking, where should I make install my programs? What is commonly used directory for this? /usr/bin? This is something I have never really known.
Last edited by coffeeandmeat (2011-08-22 05:53:46)
Offline
^ you might find this useful: http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/
there is no consensus about where you should install stuff. there is just a hierarchy with some dedicated folders, but in the end it is up to you to decide where you want to leave your software.
Offline
Crunchbang is debian. Debian uses it's own package management system, you don't really "make install" packages, I'd rather "make checkinstall" to create a minimal .deb which can be added by dpkg.
If you really insist on installing packages manually, read the link rhowaldt provided and install your "local" stuff in /usr/local/*.
I'm so meta, even this acronym
Offline
^ read it anyway, it is good information, and your system makes use of it so no wasted time there!
Offline
I already added /usr/bin to my PATH
/usr/bin should already be in your PATH, by default.
but doesn't whereis only work within that PATH variable?
No. whereis tells you where various files connected with a certain package are located. (man whereis) A possibly more useful command in this case is 'which', which checks your PATH and tells you what file would be executed if you called that particular command. (man which)
(...feeling a bit rtfm today... ?
)
John Please help us keep your forums manageable.
--------------------
( a boring Japan blog , idle twitterings and GitStuff )
#! forum moderator
Online
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.