I like how you can manage dependencies with pip requirements. Is there something similar in case of apt-get?
http://www.pip-installer.org/en/latest/requirements.html#requirements-file-format
I like how you can manage dependencies with pip requirements. Is there something similar in case of apt-get?
http://www.pip-installer.org/en/latest/requirements.html#requirements-file-format
Your question is that you want to have a list of system dependences in one file, for being able to install it with one command.
I don't recomend you to include the version of a package in the system dependencies. In the soft system dependences like "build-essential" or "uuid-dev" you normally want the latest version of the package. In the "hard dependeces" like python, postgres or whatever, normally the version is specified in the name of the package itself, like "python2.6-dev" or "postgresql-8.4". Another problem you may have defining the exact version of the package is that maybe the version 8.4.11-1 of postgresql-8.4 will not be available in the repository in three months or in a year, and you will end up installing the current version in the repo.
Example. You can create a file named "requirements.system" with the system packages you need for you project:
python-virtualenv
python2.6-dev
uuid-dev
python-pip
postgresql-8.4
Then, in your INSTALL file explain how to install the system packages.
# Install system depencences by running
cat ~/project/install/requirements.system | xargs sudo aptitude install
We have running this configuration for about two years, having to recreate the enviroment from the scrach a few times and we never had a problem.
We use the aptfile format at work. It's simply a bash wrapper with some helpers built-in.
Since apt accepts input from stdin the simplest way to do it is:
$ cat requirement.txt
gcc
cmake
$ apt install < requirement.txt
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.