[Buildroot] [pkg-perl infra 08/12] manual: adding packages perl

François Perrad francois.perrad at gadz.org
Thu Nov 21 08:47:06 UTC 2013

2013/11/20 Thomas Petazzoni <thomas.petazzoni at free-electrons.com>:
> Dear Francois Perrad,
> On Wed, 20 Nov 2013 18:01:56 +0100, Francois Perrad wrote:
>> +In fact, this file and the Config.in are written by running
>> +the script +./scancpan Foo-Bar+ in the +TOPDIR+ directory.
>> +This script creates packages for all required Perl/CPAN dependencies.
>> +All theses generated files are stored in the +package/cpan+ directory.
>> +In very specific case, this Makefile must be modified, for example : for
>> +adding a C native dependency.
>> +
>> +The Perl/CPAN modules are fine-grained, the number of module grows quickly
>> +over 100. So, only modified files will be stored in the Buildroot repository,
>> +all others can be regenerated by +scancpan+.
> I think this principle is quite problematic. If one looks at the
> "libmoose-perl: new package", it has a huge number of dependencies, and
> the vast majority of them are not available in Buildroot. One need to
> run the scancpan script to get all the packages generated.
> I unfortunately don't really have a good proposal to offer. Isn't it
> better to simply integrate all those Perl modules as normal Buildroot
> packages, and have the proper tools/scripts to update those Perl module
> packages from CPAN ? So it would be a bit like your scancpan script,
> except that packages are committed in the Buildroot Git repository, and
> with scancpan you can update those packages from CPAN and send patches
> to Buildroot to push those updates.

A BR user (a single developer or an organization) needs its own
repository for config, specific packages and final application.
At this time, I think that packages generated by `scancpan` must be
saved in an user repo and not in the BR repo.
But we really need feeback from users.


> Best regards,
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

More information about the buildroot mailing list