From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/9] perl: new package v4
Date: Mon, 27 Aug 2012 23:54:19 +0200 [thread overview]
Message-ID: <20120827235419.0486035e@skate> (raw)
In-Reply-To: <CAB0FRsuKC8Ow_Fqq+iOR3uW-iENzhX3o8qz9OCDf4rr0xb3uDQ@mail.gmail.com>
Le Mon, 27 Aug 2012 23:05:53 +0200,
Fran?ois Perrad <francois.perrad@gadz.org> a ?crit :
> miniperl is built during the full perl build, it is just a specific
> installation.
> There are no common step (configure, build of exe, build of modules,
> install) between microperl and perl.
> So, technically a merge of these packages is not easy.
Ok.
> I've updated microperl to the latest stable release.
> But I think that microperl is an useless toy which will be removed
> soon by the Perl community.
As long as the long term intention is to get rid of microperl, I'm
fine. Should we mark it "depends on BR2_DEPRECATED" ?
> I prefer spend my time with the full perl and the CPAN modules.
> There still a lot of work with Perl community for put my patches in
> the upstream.
>
> With this today version, cpanminus really cross-compiles the modules from CPAN.
> The Dancer web framework (my current goal) requires 22 modules from CPAN.
> The CPAN contains more than 23000 modules. This is the challenge.
> ? CPAN is the language, Perl is just its syntax ? - Audrey Tang.
:-)
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-08-27 21:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 15:28 [Buildroot] [PATCH 1/9] perl: new package v4 Francois Perrad
2012-08-27 15:28 ` [Buildroot] [PATCH 2/9] perl: add an option for miniperl Francois Perrad
2012-08-27 15:28 ` [Buildroot] [PATCH 3/9] cpanminus: new package v2 Francois Perrad
2012-08-27 15:28 ` [Buildroot] [PATCH 4/9] microperl: build extensions at build time Francois Perrad
2012-08-27 15:28 ` [Buildroot] [PATCH 5/9] microperl: bump version to 5.14.2 Francois Perrad
2012-08-27 15:28 ` [Buildroot] [PATCH 6/9] microperl: improve configure step on 64bits platform Francois Perrad
2012-08-27 15:28 ` [Buildroot] [PATCH 7/9] microperl: install more modules by default Francois Perrad
2012-08-27 15:28 ` [Buildroot] [PATCH 8/9] microperl: bump version to 5.16.1 Francois Perrad
2012-08-27 15:28 ` [Buildroot] [PATCH 9/9] microperl: remove host-microperl Francois Perrad
2012-08-27 19:10 ` [Buildroot] [PATCH 1/9] perl: new package v4 Thomas Petazzoni
2012-08-27 21:05 ` François Perrad
2012-08-27 21:54 ` Thomas Petazzoni [this message]
2012-08-28 12:06 ` [Buildroot] [UNSURE]Re: " François 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=20120827235419.0486035e@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