From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pkg-perl infra 07/12] host-libmodule-build-perl: new package
Date: Wed, 20 Nov 2013 18:21:37 +0100 [thread overview]
Message-ID: <20131120182137.7c1099d8@skate> (raw)
In-Reply-To: <1384966920-9454-8-git-send-email-francois.perrad@gadz.org>
Dear Francois Perrad,
On Wed, 20 Nov 2013 18:01:55 +0100, Francois Perrad wrote:
> the version coming with host-perl is too old
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/cpan/Config.in | 1 +
> package/cpan/libmodule-build-perl/Config.in | 6 ++++++
> .../libmodule-build-perl/libmodule-build-perl.mk | 16 ++++++++++++++++
> scancpan | 3 +++
> 4 files changed, 26 insertions(+)
> create mode 100644 package/cpan/libmodule-build-perl/Config.in
> create mode 100644 package/cpan/libmodule-build-perl/libmodule-build-perl.mk
>
> diff --git a/package/cpan/Config.in b/package/cpan/Config.in
> index bb98dc3..c821064 100644
> --- a/package/cpan/Config.in
> +++ b/package/cpan/Config.in
> @@ -1 +1,2 @@
> +source "package/cpan/libmodule-build-perl/Config.in"
> source "package/cpan/libxml-parser-perl/Config.in"
> diff --git a/package/cpan/libmodule-build-perl/Config.in b/package/cpan/libmodule-build-perl/Config.in
> new file mode 100644
> index 0000000..dc63312
> --- /dev/null
> +++ b/package/cpan/libmodule-build-perl/Config.in
> @@ -0,0 +1,6 @@
> +config BR2_PACKAGE_LIBMODULE_BUILD_PERL
> + bool "libmodule-build-perl"
> + depends on BR2_HOST_ONLY
I think this BR2_HOST_ONLY thing is stupid. I know we have it in
Buildroot, but we should just kill it and remove the useless Config.in
files.
> + help
> + Build and install Perl modules
> +
> diff --git a/package/cpan/libmodule-build-perl/libmodule-build-perl.mk b/package/cpan/libmodule-build-perl/libmodule-build-perl.mk
> new file mode 100644
> index 0000000..a08385b
> --- /dev/null
> +++ b/package/cpan/libmodule-build-perl/libmodule-build-perl.mk
> @@ -0,0 +1,16 @@
> +################################################################################
> +#
> +# libmodule-build-perl
> +#
> +################################################################################
> +
> +LIBMODULE_BUILD_PERL_VERSION = 0.4200
> +LIBMODULE_BUILD_PERL_AUTHOR = LEONT
> +LIBMODULE_BUILD_PERL_SOURCE = Module-Build-$(LIBMODULE_BUILD_PERL_VERSION).tar.gz
> +LIBMODULE_BUILD_PERL_SITE = $(BR2_CPAN_MIRROR)/authors/id/L/LE/LEONT/
> +#LIBMODULE_BUILD_PERL_DEPENDENCIES = perl
> +HOST_LIBMODULE_BUILD_PERL_DEPENDENCIES =
Is this needed? Maybe to remove host-perl as an automatic dependency?
In any case, having a comment on top of this line would be good.
> +LIBMODULE_BUILD_PERL_LICENSE = perl_5
> +
> +#$(eval $(perl-package))
Remove commented lines.
> +$(eval $(host-perl-package))
> diff --git a/scancpan b/scancpan
> index d8a68d6..e0ae7ba 100755
> --- a/scancpan
> +++ b/scancpan
> @@ -509,8 +509,10 @@ sub fetch {
> $dist{$name} = $result;
> my @deps_build = ();
> my @deps_runtime = ();
> + my $mb;
> foreach my $dep (@{$result->{dependency}}) {
> my $modname = ${$dep}{module};
> + $mb = 1 if $modname eq q{Module::Build};
> next if $modname eq q{perl};
> next if $modname =~ m|^Alien|;
> next if $modname =~ m|^Win32|;
> @@ -527,6 +529,7 @@ sub fetch {
> }
> fetch( $distname );
> }
> + unshift @deps_build, q{Module-Build} if $mb;
> $deps_build{$name} = \@deps_build;
> $deps_runtime{$name} = \@deps_runtime;
> }
I believe this chunk should be part of the patch adding scancpan.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-20 17:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 17:01 [Buildroot] [pkg-perl infra 00/12] a package infrastructure for Perl/CPAN modules Francois Perrad
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 01/12] perl: new infrastructure Francois Perrad
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 02/12] cpan: a home for Perl modules Francois Perrad
2013-11-20 17:23 ` Thomas Petazzoni
2013-11-20 21:03 ` François Perrad
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 03/12] cpanminus: remove it Francois Perrad
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 04/12] perl: remove useless patch Francois Perrad
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 05/12] qemu: add a Config.in.host Francois Perrad
2013-11-20 17:25 ` Thomas Petazzoni
2013-11-20 21:09 ` François Perrad
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 06/12] libxml-parser-perl: move and refactor with perl infrastructure Francois Perrad
2013-11-20 17:28 ` Thomas Petazzoni
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 07/12] host-libmodule-build-perl: new package Francois Perrad
2013-11-20 17:21 ` Thomas Petazzoni [this message]
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 08/12] manual: adding packages perl Francois Perrad
2013-11-20 17:33 ` Thomas Petazzoni
2013-11-21 8:47 ` François Perrad
2013-11-21 9:17 ` Thomas Petazzoni
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 09/12] libcurses-perl: new package Francois Perrad
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 10/12] libnet-ssleay-perl: " Francois Perrad
2013-11-20 17:01 ` [Buildroot] [pkg-perl infra 11/12] libmoose-perl: " Francois Perrad
2013-11-20 17:02 ` [Buildroot] [pkg-perl infra 12/12] libxml-libxml-perl: " Francois Perrad
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=20131120182137.7c1099d8@skate \
--to=thomas.petazzoni@free-electrons.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