Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [pkg-perl infra V3 09/12] manual: adding packages perl
Date: Wed, 05 Feb 2014 18:45:55 +0100	[thread overview]
Message-ID: <52F278D3.1020104@mind.be> (raw)
In-Reply-To: <20140204105740.GF3454@free.fr>

On 04/02/14 11:57, Yann E. MORIN wrote:
> Fran?ois, All,
> 
> On 2013-11-23 10:25 +0100, Francois Perrad spake thusly:
>> diff --git a/docs/manual/adding-packages-perl.txt b/docs/manual/adding-packages-perl.txt
>> new file mode 100644
>> index 0000000..4efc53a
>> --- /dev/null
>> +++ b/docs/manual/adding-packages-perl.txt
>> @@ -0,0 +1,91 @@
>> +// -*- mode:doc; -*-
>> +// vim: set syntax=asciidoc:
>> +
>> +Infrastructure for Perl/CPAN packages
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> +
>> +[[perl-package-tutorial]]
>> +
>> ++perl-package+ tutorial
>> +^^^^^^^^^^^^^^^^^^^^^^^
>> +
>> +First, let's see how to NOT write a +.mk+ file for a Perl/CPAN package,
>> +with an example :
> 
> I don't really like the way you introduce this by stating "how NOT to [...]".
> 
> I would prefer that you straight from the start state that they are
> generated files, and still describe all the entries later. Maybe
> something like:
> 
>     ---8<---
>     The +.mk+ files for perl packages are generated files, by running
>     the script +support/scripts/scancpan+ fron Buildroot's top
>     directory:
> 
>     ---
>     support/scripts/scancpan foo-bar
>     ---
> 
>     In most cases, this script will generate a correct +.mk+ file,
>     but in some cases (eg. when adding a native C dependency), manual
>     editing might be needed.

 Actually, in most cases manual editing is needed to add _LICENSE_FILES.

[snip]
>> +The main macro of the Perl/CPAN package infrastructure is
> 
> Since you here mix perl and cpan, I wonder if the best name for this
> infra is perl or cpan.
> 
> For example, the luarocks infra we recently added is called 'luarocks',
> as per the repository of lua paclage, not 'lua' as per the language
> name.
> 
> So maybe we should call this perl infdra cpan instead. Any comment
> against that?

 Sounds like a good idea to me. Then you also see the relation between
package/pkg-cpan.mk and package/cpan (like for cmake).


 Regards,
 Arnout

> 
> Regards,
> Yann E. MORIN.
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-02-05 17:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23  9:25 [Buildroot] [pkg-perl infra V3 00/12] a package infrastructure for Perl/CPAN modules Francois Perrad
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 01/12] perl: new infrastructure Francois Perrad
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 02/12] cpan: a home for Perl modules Francois Perrad
2014-02-04  9:01   ` Yann E. MORIN
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 03/12] scancpan: a new script Francois Perrad
2014-02-04  9:13   ` Yann E. MORIN
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 04/12] cpanminus: remove it Francois Perrad
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 05/12] perl: remove useless patch Francois Perrad
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 06/12] qemu: add a Config.in.host Francois Perrad
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 07/12] host-libxml-parser-perl: move and refactor with perl infrastructure Francois Perrad
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 08/12] host-libmodule-build-perl: new package Francois Perrad
2014-02-04 10:08   ` Yann E. MORIN
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 09/12] manual: adding packages perl Francois Perrad
2014-02-04 10:57   ` Yann E. MORIN
2014-02-05 17:45     ` Arnout Vandecappelle [this message]
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 10/12] libcurses-perl: new package Francois Perrad
2014-02-04 11:11   ` Yann E. MORIN
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 11/12] libnet-ssleay-perl: " Francois Perrad
2014-02-04 11:31   ` Yann E. MORIN
2013-11-23  9:25 ` [Buildroot] [pkg-perl infra V3 12/12] libxml-libxml-perl: " Francois Perrad
2014-02-04  8:49 ` [Buildroot] [pkg-perl infra V3 00/12] a package infrastructure for Perl/CPAN modules Arnout Vandecappelle
2014-02-04  8:55   ` Arnout Vandecappelle
2014-02-04  9:57   ` Arnout Vandecappelle

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=52F278D3.1020104@mind.be \
    --to=arnout@mind.be \
    --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