Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Christopher Larson <clarson@kergoth.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: most efficient way to map perl RH rpms to OE package names?
Date: Wed, 26 Oct 2016 08:52:37 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1610260849140.1963@ca624034.mitel.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1610260520300.17717@ca624034.mitel.com>


  never mind, i think i finally twigged to what i need ... i can see
in the include file "perl-rdepends_5.22.1.inc" how to define a
required module, such as the following "Text::*" modules:

RDEPENDS_${PN}-module-text-abbrev += "${PN}-module-exporter"
RDEPENDS_${PN}-module-text-balanced += "${PN}-module-carp"
RDEPENDS_${PN}-module-text-balanced += "${PN}-module-exporter"
RDEPENDS_${PN}-module-text-balanced += "${PN}-module-overload"
RDEPENDS_${PN}-module-text-balanced += "${PN}-module-selfloader"
RDEPENDS_${PN}-module-text-balanced += "${PN}-module-strict"
RDEPENDS_${PN}-module-text-balanced += "${PN}-module-vars"
RDEPENDS_${PN}-module-text-parsewords += "${PN}-module-carp"
RDEPENDS_${PN}-module-text-parsewords += "${PN}-module-exporter"
RDEPENDS_${PN}-module-text-parsewords += "${PN}-module-strict"
RDEPENDS_${PN}-module-text-tabs += "${PN}-module-exporter"
RDEPENDS_${PN}-module-text-tabs += "${PN}-module-strict"
RDEPENDS_${PN}-module-text-tabs += "${PN}-module-vars"
RDEPENDS_${PN}-module-text-wrap += "${PN}-module-exporter"
RDEPENDS_${PN}-module-text-wrap += "${PN}-module-re"
RDEPENDS_${PN}-module-text-wrap += "${PN}-module-strict"
RDEPENDS_${PN}-module-text-wrap += "${PN}-module-text-tabs"
RDEPENDS_${PN}-module-text-wrap += "${PN}-module-vars"
RDEPENDS_${PN}-module-text-wrap += "${PN}-module-warnings-register"

so, AFAICT, i need define only the equivalent information for
additional modules i want, and explicitly add those to the list of
modules i want built.

  seems pretty straightforward, am i overlooking anything?

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-10-26 12:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 20:53 most efficient way to map perl RH rpms to OE package names? Robert P. J. Day
2016-10-24 21:50 ` Christopher Larson
2016-10-25  6:42   ` Robert P. J. Day
2016-10-25  6:48   ` Robert P. J. Day
2016-10-25  7:05     ` Robert P. J. Day
2016-10-25 15:07       ` Christopher Larson
2016-10-26  3:20         ` Tim Orling
2016-10-26  9:48         ` Robert P. J. Day
2016-10-26 12:52           ` Robert P. J. Day [this message]
2016-10-26  9:55         ` Robert P. J. Day
2016-10-25 11:51   ` Robert P. J. Day
2016-10-25 12:11   ` Robert P. J. Day

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.1610260849140.1963@ca624034.mitel.com \
    --to=rpjday@crashcourse.ca \
    --cc=clarson@kergoth.com \
    --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