From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/13] scancpan
Date: Wed, 10 Oct 2018 09:09:32 +0200 [thread overview]
Message-ID: <20181010090932.78ff793a@windsurf> (raw)
In-Reply-To: <20181010064621.19253-1-francois.perrad@gadz.org>
Hello Fran?ois,
On Wed, 10 Oct 2018 08:46:08 +0200, Francois Perrad wrote:
> 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!
> 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.
> 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
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-10-10 7:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 6:46 [Buildroot] [PATCH 00/13] scancpan Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 01/13] scancpan: wrap abstract if too long Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 02/13] scancpan: trim the abstract Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 03/13] scancpan: sort license files Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 04/13] scancpan: sort license in hash file Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 05/13] scancpan: split multiple dependencies on multiple lines Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 06/13] scancpan: remove run-time dependencies Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 07/13] perl-*: regeneration of hash files Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 08/13] perl-*: regeneration of Config.in files Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 09/13] perl-*: regeneration of *.mk files Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 10/13] scancpan: add PERL_FOO_DISTNAME in perl-foo.mk Francois Perrad
2018-10-10 7:10 ` Thomas Petazzoni
2018-10-10 6:46 ` [Buildroot] [PATCH 11/13] perl-*: regeneration with _DISTNAME Francois Perrad
2018-10-10 6:46 ` [Buildroot] [PATCH 12/13] pkg-perl: add a target which upgrades all packages from metacpan Francois Perrad
2018-10-10 7:10 ` Thomas Petazzoni
2018-10-10 7:33 ` François Perrad
2018-10-10 8:25 ` Thomas Petazzoni
2018-10-10 6:46 ` [Buildroot] [PATCH 13/13] [RFC] pkg-perl: add per package upgrade target Francois Perrad
2018-10-10 7:09 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181010090932.78ff793a@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox