Re: Bug#747628: perl: module deprecations / removals in 5.20
Hi,
Niko Tyni wrote:
> On Sun, May 18, 2014 at 07:45:44PM +0300, Damyan Ivanov wrote:
> > -=| Niko Tyni, 17.05.2014 14:17:19 +0300 |=-
> > > These are the Perl core modules that were deprecated in 5.18 and
> > > removed from the core in 5.20. Most of the above packages were
> > > created for the 5.18 transition. The question is if the perl 5.20
> > > package need to Depend on them or if a Recommends entry is enough.
> >
> > On one hand, people who do not install Recommends will have breakage.
> > On the other, I don't see an easy way to avoid that, unless perl
> > Depends on the deprecated modules forever, which I guess is not
> > desirable.
>
> I think we only need to be concerned about upgrades breaking by vanished
> modules.
While I agree here, I don't think the reason is valid:
> That means one release cycle: once the separated packages are
> pulled in once, they will stay on the system even when the perl package
> drops the hard dependencies in the next upgrade.
Not necessarily. If people use "apt-get autoremove" as commonly
advised by "apt-get install" in such cases, or if people use aptitude,
those packages get removed once the last dependency vanished.
But I neither have an idea for a better solution. :-/
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
Reply to: