From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: perl packaging, Makefile.PL versus Build.PL?
Date: Fri, 18 Nov 2016 05:24:31 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1611180513530.24565@localhost.localdomain> (raw)
still going to have a few more questions on the standards for
packaging perl source into OE recipes, here's the first one.
as i read it, there are two build standards for perl source in OE:
cpan.bbclass: Makefile.PL build-based
cpan_build.bbclass: (newer) Build.PL build-based
so if one peruses the source at CPAN, it should be obvious which build
system is relevant, no? so what about source that has *both* those
files?
https://metacpan.org/pod/Parse::DMIDecode
which has both of those install scripts in the top-level directory,
although the INSTALL file clearly refers to the newer build system:
perl Build.PL
perl Build
perl Build test
perl Build install
does it make any logical sense for both of those files to be there?
backward compatibility? any other reason? or am i just wildly
misunderstanding something?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2016-11-18 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 10:24 Robert P. J. Day [this message]
2016-11-18 12:58 ` perl packaging, Makefile.PL versus Build.PL? Jens Rehsack
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=alpine.LFD.2.20.1611180513530.24565@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
/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