I was wondering: when installing something, there’s an easy way of double clicking an install executable file, and on the other hand, there is a way of building it from source.
This is an issue that really limits my enjoyment of Linux. If the application isn’t on a repository or if it doesn’t have an installer script, then I really struggle where and how to install an application from source.
In books, I typically read references to the Linux Source Tree at /usr/src/linux with the usual set of subdirectories (arch, block, crypto, …).
Assume I have some issue that was fixed by a recent patch to the official Linux git repository. I have a work around, but I’d like to undo it when a release happens that contains my the fix. I know the exact git commit hash, e.g. f3a1ef9cee4812e2d08c855eb373f0d83433e34c.
I do a ton of file compression. Most of the stuff I am compressing is just code, so I need to use lossless compression.
In Debian, AFAIK some packages are maintained in Subversion (famously team-pkg-gnome), while some are maintained in git, and others in some other VCS.
Is there a standard location in Linux for holding source files for example OpenSSL. I am building Nginx from source with non default version of OpenSSL. I need to download and untar OpenSSL and I did it in home directory. Now, I wonder is there a standard location in Linux maybe /opt ?
I want to read the source code of some package in Debian; how can I do that?
When installing something from source (say, Ruby 1.9.2), what command can I run to get a complete list of all the dependencies needed to install that application? Is this possible?
Is there a way to completely restart Bash and reload .bashrc and .profile and the like? I’d like to make sure my changes worked out properly after editing these files.