On Sun, 2001-12-16 at 06:16, Fabrice FACORAT wrote:
>
> Imagine I install some stuff from source ... what are you doing , is
> this is doing to break by config by overriding what I install from
> source ?
I'm not suggesting anything as totalitarian as apt's refusal to function
on a system with broken depends or even making this a default behavior.
I'm suggesting that it should be an option for those cases in which it
would be useful. As far as breaking your config, a properly written rpm
spec file won't trash your config files. It will, however still crunch
custom compiled binaries. For a long time, (until I got this new box
that will actually run a Mandrake kernel) I used dummy
kernel-{,headers,source} packages that contained no files, but satisfied
the depends.
If you have forced packages or ignore certain depends because you know
you have fulfilled the need with self-compiled software (which you might
want to put into an rpm for your own system maintenance) then this
feature would be something you would not use. I'm more looking at the
newbie who will blindly hit the force button provided by rpmdrake when
some package fails its depends check.
--
Anton Graham GPG ID: 0x18F78541
<[EMAIL PROTECTED]> RSA key available upon request
"And remember: Evil will always prevail, because Good is dumb."
-- Spaceballs
