Quoting gregor herrmann (2021-12-06 19:48:39) > I looked a bit further, and this is not as trivial as most CPAN > distributions: > > - perlimports in the CPAN tarball is a fat-packed script: > https://metacpan.org/dist/App-perlimports/source/script/perlimports > i.e. it embeds a couple of Perl modules; > now we could just live it but that's neither elegant nor clever > seurity-wise nor simple copyright-wise; > - we could try to rip out the fat-packed parts (which still leaves > the copyright question for the source package); [0] but: > - the fat-packing works with an author script: > https://github.com/oalders/App-perlimports/tree/main/author > which already says that it uses a forked PPI module (cf. also > .gitmodules in the upstream git repo) > > With cpanminus we have a similar situation, there we take the tarball > from GitHub and not from CPAN, and create the actual script without > fatpacking. (Before that we removed the fatpacked modules from the > script.) > > But this forked PPI seems like a blocker, at least I have no good > idea how to handle it right now. [1] If the forked PPI is specific for building this module, I would find it sensible to embed that fork with this source package - e.g. using the "component" feature of uscan. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Attachment:
signature.asc
Description: signature