On Tue, 06 Sep 2011, Michael Tautschnig wrote:
> [...]
> >
> > The problem is that perl and perl-modules really are one package that was
> > split apart solely to get the (large) architecture-independent parts into
> > an arch: all package.
> >
>
> Wouldn't this problem be solved by moving the contents of perl to, e.g.,
> perl-bin, making perl a dummy package, and the following relations:
>
> Package: perl
> Depends: perl-bin, perl-modules
>
> Package: perl-bin
>
> Package: perl-modules
> Depends: perl-bin (= ${Source-Version})
>
> But this solution seems so simple that I must be missing something.
You miss the fact that installing perl-bin alone can also break
stuff trying to use what's in that package if perl-modules is not
installed.
That said with such a setup, it's unlikely to happen given that
most dependencies point to "perl" which enforces the presence of
both packages. And even the bogus dependency on perl-modules does
the right thing.
So it's certainly better than switching perl-modules's Depends to a
Recommends.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHertzog.fr (Français)
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110906095739.gc1...@rivendell.home.ouaza.com
