Your message dated Wed, 29 Apr 2015 08:48:57 +0200 with message-id <[email protected]> and subject line Re: dh_perl support for packages embedding perl has caused the Debian Bug report #739249, regarding dh_perl support for packages embedding perl to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 739249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739249 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: debhelper Version: 9.20131227 Severity: wishlist The inn and inn2 packages, which use an embedded perl interpreter, currently do this to express a proper dependency on perlapi-* (see #182089): dh_gencontrol -u-VPERLAPI=$$(perl -MConfig -e 'print "perlapi-" . ($$Config{debian_abi} || $$Config{version})') dh_perl adds a perlapi dependency only to packages which contain XS modules, so it would be nice if it could either recognize packages which have an embedded perl interpreter or have a flag to force this behaviour. (I see that it also would add a versioned dependency on perl, is it actually needed in my case?) -- ciao, Marco
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---On Mon, 17 Feb 2014 19:41:44 +0200 Niko Tyni <[email protected]> wrote: > On Mon, Feb 17, 2014 at 10:54:00PM +1100, Brendan O'Dea wrote: > > On 17 February 2014 13:20, Marco d'Itri <[email protected]> wrote: > > > > dh_perl adds a perlapi dependency only to packages which contain XS > > > modules, so it would be nice if it could either recognize packages which > > > have an embedded perl interpreter or have a flag to force this > > > behaviour. > > > > It has been some time since I looked at this, but according to policy > > you should not need a dependency on perlapi* at all: > > That's my understanding as well. > > > I can see an argument however for also adding a perlapi* dependency > > for packages which embed Perl, given that a non-trivial implementation > > will be using just as much of the Perl internals as a typical XS > > module. This would require both a policy change, and an update to > > dh_perl. > > > > Niko: have there been cases where a dependency on both libperl5.x and > > perlapi-5.X.y would have been different that just having the first > > dependency? I can imagine cases where ABI compatibility was broken by > > minor versions, but don't recall an instance myself. > > No, I don't think that has actually happened. > > I would expect that an ABI incompatibility that forces a change to the > perlapi name would also mean an SONAME change (+package rename) for > libperl, and vice versa. This is what happens with major upgrades anyway. > -- > Niko Tyni [email protected] > > Ok, I will be closing this bug against debhelper since it sounds like the necessary features are already available via shlibs system. Thanks, ~Niels
--- End Message ---
