On Mon, May 12, 2008 at 10:45:47AM +0000, Thomas Viehmann wrote: > tag 480458 moreinfo > thanks > > Hi, with a huge number of reverse build-dependencies, I think this needs a > better > plan.
> ** spf-tools-perl has an unsatisfied dependency on i386: libversion-perl > ** libconfig-json-perl has an unsatisfied dependency on i386: libversion-perl [...] Hi, perl-modules Provides: libversion-perl since 5.10.0, and none of those 25 or so packages have a versioned dependency (which can't be provided). The non-build-dependencies shouldn't be a problem, apt will select perl-modules instead just like it does with libnet-perl currently. As for building, perl-modules is currently always installed because dpkg-dev is build-essential and pulls it in. It's not build-essential itself, though. Conclusion: everything should Just Work (tm), but there's an argument for requiring build dependencies on 'perl-modules (>= 5.10.0)' for these. Possibly even 'perl-modules (>= 5.10.0) | libversion-perl' to ease backporting, but that's mostly cosmetics as at least sbuild won't look at the alternative anyway. Cc'ing debian-perl for input. Do we need to change those 25 packages before we can get rid of the other copy of version.pm? -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]