From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: meta-perl vs meta-cpan: [lib]module-build-perl-native
Date: Fri, 25 Nov 2016 04:28:24 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1611250416280.8610@ca624034.mitel.com> (raw)
about to go back and try to follow that thread about OE and perl
modules, but one question about quick and dirty workarounds ... i just
ran into the (inevitable) situation where the "standard" OE layers and
meta-cpan have different naming conventions for modules, as in:
meta-perl: DEPENDS += "libmodule-build-perl-native
meta-cpan: DEPENDS += "module-build-perl-native"
which finally bit me when i wanted to add to an image the one (the
*only* one) meta-perl recipe that contains:
$ grep -r "module-build-perl-native" *
meta-perl/recipes-perl/libhtml/libhtml-tree-perl_5.03.bb:DEPENDS += "libmodule-build-perl-native \
$
which clashed trying to install files into a shared area when those
files already exist, given that numerous recipes from meta-cpan
already contain:
$ grep -hr "module-build-perl-native" *
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
$
i'm actually surprised there is just the one recipe that eventually
got me into trouble, and while i understand there's a long-term plan
to standardize this, what is the best short-term hack to get around
this? reproduce the recipe? .bbappend and override DEPENDS? blacklist
the one from meta-cpan and replace it?
and in the long term, unless there's a common naming convention, how
can meta-cpan be listed as an OE layer at
https://layers.openembedded.org/layerindex/branch/master/layers/?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
reply other threads:[~2016-11-25 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1611250416280.8610@ca624034.mitel.com \
--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