views:

388

answers:

1

Here's what I would like. Start with a virtual sytem with no installed packages. Then I invoke a tool similar to apt-get to ask it to compute the dependencies and mark all the packages that would be installed as installed. Let this be clear: it says the packages are installed, but they are no files actually installed.

Then if I ask for more packages to be "installed", it may propose to add or remove other packages. It wouldn't actually remove packages, but obviously just mark them removed.

Now, how would this be useful? I would like to be able to test the installation of packages on a bare Debian or Ubuntu system. I want to know if a package is installable given a certain scenario. To do this with actual installation would take a lot of disk space and time.

APT has a "simulate" option, but it does not mark packages as installed.

+3  A: 

You're probably best off hooking into one of the scripting interfaces that Debian has for their various package tools and writing your own simulator.

(Edit: I can't find dpkg-perl and dpkg-python anymore. dpkg-awk and dpkg-ruby exist, but they don't look like they'll do the job.)

However: Debian has a tool "equivs" that lets you build "empty" packages that just satisfy dependencies, but install no files beyond the control files. http://packages.debian.org/search?keywords=equivs

dpkg and apt-get both have options to run with different administration and root directories. The dpkg man page has them, but the apt-get one is buried in apt.conf.

DIRECTORIES

The configuration item RootDir has a special meaning. ...

aptitude lets you pick and choose what to install, and then "commits" it by running dpkg and/or apt with the right settings. Playing around with it might be sufficient for some of your needs, though you'll want to save the settings before hand, and restore afterword.

wnoise
Can you point me to one of these scripting interfaces you mention?
Nicolas Marchildon