On Fri, Apr 29, 2011 at 09:48:27AM +0300, Niko Tyni wrote: > The perl package has carried a change to ExtUtils::Install since forever. > > > http://patch-tracker.debian.org/patch/series/view/perl/5.10.1-18/debian/extutils_hacks.diff > > This should be reviewed and applied also to the separate > libextutils-install-perl package and/or upstream if found necessary, > or removed from the perl package otherwise. > > There's little point in patching the core version if the patch gets > overridden when installing the separately packaged version.
This but isn't a problem any more, because libextutils-install-perl has been removed. > It looks like the only relevant change in the above bundle is > > * Respect umask during installation, and set as appropriate for each of > perl, vendor and site (policy requires group writable site dirs). > > but I haven't looked at this very hard. While looking at this I realised that this was a fairly big patch made up of several independent changes, so I took the opportunity to split the patch into independent chunks: debian/libperl_embed_doc.diff - standalone doc fix for #186778 fixes/respect_umask.diff - this could be sent upstream; it shouldn't change the behaviour of the build - unfortunately it's patching two separate CPAN distributions at once, so probably won't be easy to get patched upstream. debian/writable_site_dirs.diff - this applies on top of the above and implies our policy debian/extutils_set_libperl_path.diff - set libperl path for our builds debian/no_packlist_perllocal.diff - don't install .packlist or perllocal.pod debian/prefix_changes.diff - EU::MM changes to PREFIX We could theoretically forward fixes/respect_umask.diff, but we probably need to think a bit more about whether it makes sense to do so, and what the dependencies of the changes in both CPAN distributions in question are. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
