All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: mulhern <mulhern@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Discovering available Perl modules OR writing recipes for your own
Date: Thu, 25 Jul 2013 14:44:37 +0100	[thread overview]
Message-ID: <5546180.0Max780gjA@helios> (raw)
In-Reply-To: <CADM5y7v6xs5iaUtnt8hWypAgRz981Sx90nSLHb9NM5F6BoNidw@mail.gmail.com>

Hi mulhern,

On Thursday 25 July 2013 09:25:04 mulhern wrote:
> Thanks, but that specific module isn't the whole total of my problem. It's
> nice of you to point out for me the location of that one but what about the
> more like 15 or so others I didn't list and where they might or might not
> be hiding? Should that particular module really be in the meta-security
> layer just because it is meta-security that needed it first? 

I think the problem is we still don't have a good home for perl recipes not 
needed by anything in OE-Core but that are still useful. I am aware that a 
community member is working on a large number of perl recipes for CPAN modules 
(Stygia on IRC) but I'm not sure what the current status of that work is.

> My real problem is not that particular module it's that
> 1) I don't know a good way to find out if all those modules that I need
> haven't already been packaged up by someone somewhere.

The best way we have for finding these is the recipe search function in the OE 
layer index:

http://layers.openembedded.org/layerindex/recipes/

> 2) I'm not certain that writing a separate recipe for each and every one of
> those little modules is the correct way to go about getting them all if
> they aren't already available somewhere.

This is the convention we have established. Hopefully with what's in OE-Core, 
meta-security and what's coming in the new layer I referred to above we'll on 
our way to a sizable portion of the packages available. It might be worth 
pinging Stygia to find out how work is going on that layer.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-07-25 13:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 15:30 Discovering available Perl modules OR writing recipes for your own mulhern
2013-07-25 11:52 ` Trevor Woerner
2013-07-25 13:25   ` mulhern
2013-07-25 13:44     ` Paul Eggleton [this message]
2013-07-25 14:22     ` Trevor Woerner
2013-07-25 14:57       ` mulhern
2013-07-27  4:03 ` Stewart, David C
2013-07-27 12:24   ` mulhern

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=5546180.0Max780gjA@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=mulhern@gmail.com \
    --cc=yocto@yoctoproject.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 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.