All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Tim O'Callaghan <tocallaghan@meyn.com>
Cc: yocto@yoctoproject.org
Subject: Re: How to avoid re-creating a recipe (+my meta-bucket approach)
Date: Wed, 17 Oct 2012 09:49:37 +0100	[thread overview]
Message-ID: <2287710.4FdqJpfmq4@helios> (raw)
In-Reply-To: <12F9B0C37BAC49429468AA27112A5F5B37B94DF4@DB3PRD0510MB368.eurprd05.prod.outlook.com>

On Wednesday 17 October 2012 08:39:36 Tim O'Callaghan wrote:
> After seeing the lmsensors thread float by I thought it about time I started
> the discussion on how people manage to avoid re-inventing recipes, and to
> get the ball rolling, I thought I would describe mine.
> 
> As I do not have the any idea what recipes may be kicking about, I devised
> what I call the meta-bucket approach. It is pretty simple, I have a script
> that clones every existing OE/Yocto repository I know about into one easily
> grep-able place[1].
> 
> The to the main question, how are others managing this?

I clone the layer repositories most likely to hold new recipes and then use 
some scripts I wrote to process them into a list of recipes that can be easily 
searched using grep. I wouldn't mind sharing those scripts if some people 
would find them useful.

However, what I hope we can do in the 1.4 timeframe would be to implement my 
proposal here:

 https://bugzilla.yoctoproject.org/show_bug.cgi?id=3272

This would provide us with a way to search all published layers down to the 
recipe level from the web.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2012-10-17  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17  8:39 How to avoid re-creating a recipe (+my meta-bucket approach) Tim O'Callaghan
2012-10-17  8:49 ` Paul Eggleton [this message]
2012-10-17 18:09   ` Philip Balister
2012-10-17 15:14 ` Tom Zanussi

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=2287710.4FdqJpfmq4@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=tocallaghan@meyn.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.