Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: how to add new perl modules to stock OE build?
Date: Thu, 27 Oct 2016 08:46:23 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1610270833260.15014@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.20.1610270533590.12908@localhost.localdomain>


  ack ... never mind, i see my fundamental misunderstanding. i thought
all of the recipes being processed via the "perl-modules" package were
being (if necessary) downloaded from CPAN, or something like that,
then turned into installable rpms. i didn't look closely enough into
the perl source to see that all the modules listed in
"perl-rdepends_5.22.1.inc" are already in the perl source tree.

  so i'm back to my original question -- what is the proper way to add
arbitrary perl modules to an image? if someone has a simple example of
how it's done, that'd be great. as proof-of-concept, i'd like to add
the Text::Template module to my "qemuppc" target.

  thoughts? sorry for all the earlier noise, i thought i had it
figured out but ... no.

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-27 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27  9:52 how to add new perl modules to stock OE build? Robert P. J. Day
2016-10-27 12:46 ` Robert P. J. Day [this message]
2016-10-27 13:26   ` Olof Johansson
2016-10-27 13:55     ` 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.1610270833260.15014@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