[opensuse-packaging] noarch perl packages
Hi, Many pure perl packages are not noarch just because of that .packlist file in %perl_vendorarch. Is that file good for anything in an rpm managed system? Ie could it be savely omitted from packages? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday 2010-02-22 13:18, Ludwig Nussel wrote:
Many pure perl packages are not noarch just because of that .packlist file in %perl_vendorarch. Is that file good for anything in an rpm managed system? Ie could it be savely omitted from packages?
I don't really see the use for it either. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday 22 February 2010, Ludwig Nussel wrote:
Many pure perl packages are not noarch just because of that .packlist file in %perl_vendorarch. Is that file good for anything in an rpm managed system?
it is there to make "perlivp" succeed - which is required for upstream to accept bugreports (I think).
Ie could it be savely omitted from packages?
it could, but you have to convince the "perl" maintainer to accept a patch for perlivp ;) Some distros (Debian iirc?) strips those files. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Dirk Müller wrote:
On Monday 22 February 2010, Ludwig Nussel wrote:
Many pure perl packages are not noarch just because of that .packlist file in %perl_vendorarch. Is that file good for anything in an rpm managed system?
it is there to make "perlivp" succeed - which is required for upstream to accept bugreports (I think).
Ie could it be savely omitted from packages?
it could, but you have to convince the "perl" maintainer to accept a patch for perlivp ;)
The perlivp problem apparently is an unrelated problem that needs to be fixed independently.
Some distros (Debian iirc?) strips those files.
The .packlist files are processed by ExtUtils::Installed. That one must have been broken for ages though. It doesn't search the "vendorarchexp" directory where our .packlist files are installed. The usefulness of those .packlist files for perl modules that were installed via rpm are questionable anyways. After sufficient pestering mls agreed that it's ok to delete the .packlist files :-) So let's get rid of %perl_process_packlist and /var/adm/perl-modules/. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (3)
-
Dirk Müller -
Jan Engelhardt -
Ludwig Nussel