On Sun, 01 Jun 2014 19:58:31 +0300, Niko Tyni wrote:
> On Sun, Jun 01, 2014 at 05:53:28PM +0200, gregor herrmann wrote:
> > I've tried this for libcommon-sense-perl now, with the idea taken from dh_perl(1):
> Looks OK to me. The PERL_CURRENT + PERL_NEXT stuff probably isn't
> needed anymore.
On Sun, 01 Jun 2014 10:03:13 -0700, Russ Allbery wrote:
> gregor herrmann <gregoa@debian.org> writes:
>
> > Does this look correct?
>
> > (For perl 5.18.2 in sid we get as expected:
> > Depends: perl (>= 5.18.2~), perl (<< 5.18.3~), perlapi-5.18.2
> > And for perl 5.20.0:
> > Depends: perl (>= 5.20.0~), perl (<< 5.20.1~), perlapi-5.20.0-exp1
> > (and the files end up in ./usr/lib/x86_64-linux-gnu/perl5/5.20/).
> > )
>
> In the long run, you'd be able to drop the versioned dependencies on perl,
> right? Because now, with versioned vendorarch directories, the perlapi
> dependency will do everything you need.
>
> In fact, as soon as Perl 5.20 is the default, or for any packages that
> depend on it, I think you can drop the versioned perl dependencies
> immediately.
Thanks Niko and Russ for the review and your thoughts on the version
constraints.
I have to admit that I'm still a bit confused by this question. My
thoughts/concerns/questions are:
- My understanding is that perlapi-$VERSION is going to be increased
for each release; is this correct? (I _think_ that thasn't always
happened in the past, or at least several versions have been
provided by one version of perl-base [0].)
If a 5.20.1 upload will only provide perlapi-5.20.1 then we indeed
don't need the additional version constraints; but this also means
a transition with several hundred binNMUs for each minor perl
release, if I'm not mistaken. (Not the issue here but I was
wondering ...)
- But still, even if perlapi-$VERSION will be increased and will be
unique in the future, this doesn't help for the current perl
versions in unstable/testing/stable/oldstable. Or should we say
that we don't expect newer versions of 5.{10,14,18} anyway and a
backport rebuilt in an up2date unstable/testing/stable/oldstable
chroot will get the higher perlapi-* dependency and that should be
enough?
[0]
5.10.1-17squeeze6 -> perlapi-5.10.0, perlapi-5.10.1
5.14.2-21+deb7u1 -> perlapi-5.14.2
5.18.2-4 -> perlapi-5.18.1, perlapi-5.18.2
On Sun, 01 Jun 2014 19:58:31 +0300, Niko Tyni wrote:
> FWIW I think eventually dh_perl should be changed, possibly with
> something like the attached patch (which I haven't found the
> time to test properly yet.)
Yay! That would be much better than messing around in debian/rules
manually.
(Not tested but it looks good.)
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Tom Waits: Metropolitan Glide
Attachment:
signature.asc
Description: Digital Signature