From b8cb320ce75caacdb3b99d0ffdc8701c0bdcc2c7 Mon Sep 17 00:00:00 2001 From: Niko Tyni Date: Fri, 30 May 2014 14:10:22 +0300 Subject: [PATCH] All packages using Perl vendorarch directory need a perlapi-* dependency Having $Config{vendorarch} change between Perl major versions (for multiarch or other reasons) implies that packages using it need a strict dependency on those versions of perl-base that have a compatible search path (@INC). The vast majority of these packages are binary ("XS") modules, where we already require a dependency on the virtual package perlapi-*, provided by perl-base. The name of this virtual package will change when the interface between the Perl interpreter and the modules changes. If we consider @INC part of that interface, we can use the existing mechanism also for the few nonbinary modules using $Config{vendorarch}. This is a new requirement that currently affects six packages in the archive. --- perl-policy.sgml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/perl-policy.sgml b/perl-policy.sgml index c23f7c3..12cd82c 100644 --- a/perl-policy.sgml +++ b/perl-policy.sgml @@ -388,14 +388,15 @@ $(MAKE) install DESTDIR=$(CURDIR)/debian/<tmp> - Binary Modules + Binary and Other Architecture Dependent Modules

Binary modules must specify a dependency on either perl or perl-base with a minimum version of the perl package - used to build the module, and must additionally depend on - the expansion of - perlapi-$Config{debian_abi} using + used to build the module. Additionally, all binary modules + (regardless of their installation directory) and any other modules + installed into $Config{vendorarch} must depend on the + expansion of perlapi-$Config{debian_abi} using the Config module. If $Config{debian_abi} is empty or not set, $Config{version} must be used.

-- 2.39.2