From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v9 06/10] cpanminus: new package
Date: Mon, 8 Oct 2012 11:37:10 +0200 [thread overview]
Message-ID: <20121008113710.4d01376c@skate> (raw)
In-Reply-To: <1349531633-26717-6-git-send-email-francois.perrad@gadz.org>
Dear Francois Perrad,
On Sat, 6 Oct 2012 15:53:49 +0200, Francois Perrad wrote:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/Config.in | 5 ++++
> package/cpanminus/Config.in | 36 +++++++++++++++++++++++
> package/cpanminus/cpanminus.mk | 46 ++++++++++++++++++++++++++++++
> package/perl/perl-fix-Module-Build.patch | 16 +++++++++++
> 4 files changed, 103 insertions(+)
> create mode 100644 package/cpanminus/Config.in
> create mode 100644 package/cpanminus/cpanminus.mk
> create mode 100644 package/perl/perl-fix-Module-Build.patch
One thing that I'm wondering with cpanminus is how it interacts with
the Buildroot mechanisms for download.
I.e :
*) Where does cpanminus downloads the Perl module tarballs?
*) Does it re-use the downloaded tarballs between rebuilds?
*) Is there a way to tell it to download its tarballs in $(DL_DIR) ?
*) Is there a way to have "make source" work properly, i.e ask
cpanminus to download the tarballs that it will need so that
offline builds are possible.
*) Is it possible to make it play nice with BR2_PRIMARY_SITE ?
Thanks!
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-10-08 9:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 13:53 [Buildroot] [PATCH v9 01/10] host-qemu: new package Francois Perrad
2012-10-06 13:53 ` [Buildroot] [PATCH v9 02/10] perl: " Francois Perrad
2012-10-08 9:34 ` Thomas Petazzoni
2012-10-08 11:41 ` François Perrad
2012-10-08 11:49 ` Thomas Petazzoni
2012-10-08 16:56 ` François Perrad
2012-10-08 19:13 ` Thomas Petazzoni
2012-10-10 14:41 ` François Perrad
2012-10-06 13:53 ` [Buildroot] [PATCH v9 03/10] perl: add DB_File Francois Perrad
2012-10-06 13:53 ` [Buildroot] [PATCH v9 04/10] gdbm: new package Francois Perrad
2012-10-06 13:53 ` [Buildroot] [PATCH v9 05/10] perl: add GDBM_File Francois Perrad
2012-10-06 13:53 ` [Buildroot] [PATCH v9 06/10] cpanminus: new package Francois Perrad
2012-10-08 9:37 ` Thomas Petazzoni [this message]
2012-10-10 15:04 ` François Perrad
2012-10-06 13:53 ` [Buildroot] [PATCH v9 07/10] perl: add option "custom install" Francois Perrad
2012-10-06 13:53 ` [Buildroot] [PATCH v9 08/10] perl: relax microperl dependencies Francois Perrad
2012-10-06 13:53 ` [Buildroot] [PATCH v9 09/10] microperl: mark as DEPRECATED Francois Perrad
2012-10-06 13:53 ` [Buildroot] [PATCH v9 10/10] microperl: remove it 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=20121008113710.4d01376c@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