On Sun, Dec 15, 2019 at 11:26:34AM +0100, Helmut Grohne wrote: > I fear that your other mail made me realize a mistake though. Unlike > python there is no standard installation. For perl it's perl-base and > perl. We cannot take perl for granted. Now perl pulls libperl5.30, which > contains extensions and we must preserve the architecture constraint > from our pure perl module to the relevant extension modules used from > libperl5.30.
I don't understand. AFAICS if the interpreter needing the modules is /usr/bin/perl, the perl:any dependency will pull in compatible standard library extension modules: the perl -> perl-base dependency guarantees perl will be the same arch as /usr/bin/perl, and the perl -> libperl5.30 dependency pulls in the modules for that architecture. If it's an embedded interpreter, a compatible set of those is already shipped with the interpreter (in libperl5.30). So where's the problem here? -- Niko
