From: Tom Zanussi <tom.zanussi@intel.com>
To: Tim O'Callaghan <tocallaghan@meyn.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: How to avoid re-creating a recipe (+my meta-bucket approach)
Date: Wed, 17 Oct 2012 10:14:05 -0500 [thread overview]
Message-ID: <1350486845.1710.40.camel@empanada> (raw)
In-Reply-To: <12F9B0C37BAC49429468AA27112A5F5B37B94DF4@DB3PRD0510MB368.eurprd05.prod.outlook.com>
On Wed, 2012-10-17 at 08:39 +0000, Tim O'Callaghan wrote:
> Hi,
>
> 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?
>
> Best regards,
>
> Tim.
> [1] https://github.com/timoc/meta-bucket
>
I do a similar thing - clone all the repos I can think of, and then have
OpenGrok index them all. That makes everything available as a fully
searchable cross-referenced set of web pages. Couldn't live without
it...
http://hub.opensolaris.org/bin/view/Project+opengrok/
Tom
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2012-10-17 15:14 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
2012-10-17 18:09 ` Philip Balister
2012-10-17 15:14 ` Tom Zanussi [this message]
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=1350486845.1710.40.camel@empanada \
--to=tom.zanussi@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.