Skip to content

scancpan

Thomas Petazzoni buildroot 1 version New

Get series with b4
b4 am 20181010090932.78ff793a@windsurf

Versions newest first

  1. v1 Latest3 of 13 patches 0 repliesNew

3 of 13 patches are in this archive. The cover letter announces 13.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
10/13scancpan: add PERL_FOO_DISTNAME in perl-foo.mk+0 -00 replies
12/13pkg-perl: add a target which upgrades all packages from metacpan+0 -01 reply
12/13pkg-perl: add a target which upgrades all packages from metacpan+0 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Buildroot] [PATCH 00/13] scancpan

Hello Fran?ois,

Quoted 2 lines · Francois Perrad

Without runtime dependencies, the build time is speed up (in parallel mode). And now, I can upgrade easily all perl modules.

Thanks a lot for this patch series!

Quoted 10 lines

Francois Perrad (13):
scancpan: wrap abstract if too long
scancpan: trim the abstract
scancpan: sort license files
scancpan: sort license in hash file
scancpan: split multiple dependencies on multiple lines
scancpan: remove run-time dependencies
perl-*: regeneration of hash files
perl-*: regeneration of Config.in files perl-*: regeneration of *.mk files

I have applied all patches up to this point.

One thing that would be nice is to adjust the Config.in generation logic to add a "# runtime" comment after the runtime dependencies. In practice it will be all target dependencies, but it is a convention we have in other packages, so it would be good to comply with it as well, and it's easy to do thanks to those packages being auto-generated.

Quoted 4 lines

scancpan: add PERL_FOO_DISTNAME in perl-foo.mk perl-*: regeneration with _DISTNAME
pkg-perl: add a target which upgrades all packages from metacpan [RFC] pkg-perl: add per package upgrade target

For this one, I'll leave a bit more time, so that other Buildroot developers can say what they think about it. In general, I like the idea. I'm not sure how applicable a per-package <pkg>-upgrade target is going to be to non-Perl packages, but let's see what other people think.

Best regards,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Read the cover letter in its thread