From: Jamie Lenehan <lenehan@twibble.org>
To: Stelios Koroneos <skoroneos@digital-opsis.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: CPAN module naming
Date: Sun, 29 Apr 2007 22:55:25 +1000 [thread overview]
Message-ID: <20070429125525.GA8230@twibble.org> (raw)
In-Reply-To: <HOECLKEKOHLAMMGDLLBHGEACKOAA.skoroneos@digital-opsis.com>
On Sun, Apr 29, 2007 at 02:45:23PM +0300, "Stelios Koroneos" wrote:
> Is there an RFC or suggestion on how the CPAN modules .bb files should be
> named ?
lib<name>-perl_<version>.bb
where "name" is the name of the package as downloaded. So for:
Algorithm-Diff-1.1902.tar.gz
we end up with:
libalgorithm-diff-perl_1.1902.bb
This naming matches that used by debian based distros (you can always
check the naming used on a debian distro to verify what it should be
called.)
Note also that the current cpan.bbclass won't handle anything
particularly complex (in particular things that contain additional
multiple Makefile.PL's in subdirectories). Once I have perl 5.8.8 as
default I'll be re-doing the way cpan.bbclass and perl-native work to
make this a lot more reliable.
--
Jamie Lenehan <lenehan@twibble.org>
next prev parent reply other threads:[~2007-04-29 13:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 10:57 perl 5.8.8 is ready Jamie Lenehan
2007-04-28 16:19 ` Rolf Leggewie
2007-04-29 12:59 ` Jamie Lenehan
2007-04-29 15:36 ` Rolf Leggewie
2007-04-29 10:51 ` Junqian Gordon Xu
2007-04-29 11:43 ` Stelios Koroneos
2007-04-29 11:45 ` CPAN module naming Stelios Koroneos
2007-04-29 12:55 ` Jamie Lenehan [this message]
2007-04-29 13:05 ` perl 5.8.8 is ready Jamie Lenehan
2007-04-29 19:40 ` Junqian Gordon Xu
2007-04-30 7:00 ` Junqian Gordon Xu
2007-04-30 8:00 ` Jamie Lenehan
2007-05-01 5:14 ` Junqian Gordon Xu
2007-05-02 0:36 ` Jamie Lenehan
2007-05-02 4:05 ` Junqian Gordon Xu
2007-05-07 18:38 ` Rolf Leggewie
2007-05-08 1:22 ` Jamie Lenehan
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=20070429125525.GA8230@twibble.org \
--to=lenehan@twibble.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=skoroneos@digital-opsis.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.