Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
There is also a $HOME/bin/ directory. It is usually used for your own scripts, but could be used for your own apps. Otherwise, it doesn't matter. Put them in a directory you create in your $HOME/ directory and add that directory to your $PATH/ variable.
Better not. $PATH has length limit, also every path will be searched after you or script invoke most commands, so less is better. Create a directory for applications in your $HOME for example $HOME/apps and extract these archives there within apllication name as directory. Then create symlink to starting application in your $HOME/bin.
I'm not sure if I'll have a lot of "portable" apps but I've only started using Linux and I already have a few of them. And they are meant to be "portable". For example Virtual Volumes View or XnViewMP.
I install such apps into /opt - including xnviewmp.
Most well-behaved programs don't need write access to the folder they are installed in, and will create what they need in the user's home folder (I have ~/.xnviewmp). Only in rare cases (for example: Wunderlist) do you have to install the code into your home folder.