Previously Julian Gilbey wrote:
> Agreed. I presume that ldconfig exists on all systems, though.
All systems Debian currently runs on anyway. I kind of expect that to
change at some point though.
> Please explain; I don't know what you mean here.
I'll have to get back to you on that :)
> Are w
On Thu, Mar 15, 2001 at 01:40:47PM +0100, Wichert Akkerman wrote:
> Previously Julian Gilbey wrote:
> > But what does it mean for a "suggests to take effect"?
>
> (Pre-)Depends, Conflicts and Replaces are the only ones that dpkg
> cares about, the others are for frontends like dselect. A Suggests
Wichert Akkerman <[EMAIL PROTECTED]> wrote:
> It should say what it currently says.
>> 7.2 Depends: should also mention "or if it is required by the
>> postinst, prerm or postrm scripts".
> Remove postrm from there, that can't rely on the Depends being present.
Is this just "postrm purge" o
Previously Julian Gilbey wrote:
> But what does it mean for a "suggests to take effect"?
(Pre-)Depends, Conflicts and Replaces are the only ones that dpkg
cares about, the others are for frontends like dselect. A Suggests
can't really take affect.
>
> > > 7.2 Depends: should also mention "or if
On Thu, Mar 15, 2001 at 03:00:14AM +0100, Wichert Akkerman wrote:
> Previously Julian Gilbey wrote:
> > 7.2 Binary dependencies
> > This section states that "All but Pre-Depends and Conflicts take
> > effect only when a package is to be configured." But actually,
> > dpkg appears to ig
Previously Julian Gilbey wrote:
> 7.2 Binary dependencies
> This section states that "All but Pre-Depends and Conflicts take
> effect only when a package is to be configured." But actually,
> dpkg appears to ignore everything except for (Pre-)Depends,
> (sometimes) Recommends and C
6 matches
Mail list logo
