Re: 3.3 configure static

[Erik Poupaert <erik dot poupaert at skynet dot be>]

> rpm ... That way, if someone installes on a machine with libraries that are
> too old, she'll be told what packages to update.

Either the deployment must be -- top on -- self-contained from the start, or else the
deployment software must do the dependency calculations and required update by
itself.

I can't ask users to start hunting for additional packages somewhere. That is, by the
way, what often happens, when you try to install an rpm you've downloaded somewhere.
You try to install, just to figure out that you need another one to find+download
from somewhere, and another one,... It's a recursive headache.

It won't fly with users who are little proficient in linux; and contribute to its
undeserved reputation for being difficult to use.