Specifying multiple binary package dependencies

[Colin Law]

On Sat, 19 Mar 2022, 22:53 Sam Varshavchik, <mrsam at courier-mta.com> wrote:

> Colin Law writes:
>
> > On Sat, 19 Mar 2022 at 12:33, Sam Varshavchik <mrsam at courier-mta.com>
> wrote:
> > >
> > > My question was a technical, rather than a policy one: if an installed
> > > package A "Depends" on B, apparently you can end up with dpkg removing
> B
> > and
> > > not doing anything about A. That just does not compute for me. My
> question
> > > was that if merely specifying that A "Depends" on B is insufficient,
> then
> > > what is?
> > >
> > > If the answer here is "well, the policy says don't do it", then that's
> just
> > > my indirect answer: no, this cannot be enforced by deb packages'
> > > dependencies.
> >
> > This thread is well beyond my knowledge base, but have you tried
> > installing and removing via apt rather than dpkg
>
> No, not yet. It's on my todo list; but first I wanted to make sure I
> understood fully how inter-package dependencies were supposed to work.
>


The reason I asked is that I am pretty sure that, with apt, if you install
a package that pulls in others, then if you uninstall the pulled in then
apt wants to remove the main package.  However, it may be that this is a
feature of apt rather than dpkg.  I don't know though.  I think perhaps
this is not the best place to ask such questions.   Perhaps
ubuntu-devel-discuss (
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss) might be
better, though there may be a Debian list too.

If you do find the solution elsewhere then please come back and tell us.

Colin

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20220320/c0aca137/attachment.html>