* How to avoid re-creating a recipe (+my meta-bucket approach)
@ 2012-10-17 8:39 Tim O'Callaghan
2012-10-17 8:49 ` Paul Eggleton
2012-10-17 15:14 ` Tom Zanussi
0 siblings, 2 replies; 4+ messages in thread
From: Tim O'Callaghan @ 2012-10-17 8:39 UTC (permalink / raw)
To: yocto@yoctoproject.org
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to avoid re-creating a recipe (+my meta-bucket approach)
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
1 sibling, 1 reply; 4+ messages in thread
From: Paul Eggleton @ 2012-10-17 8:49 UTC (permalink / raw)
To: Tim O'Callaghan; +Cc: yocto
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to avoid re-creating a recipe (+my meta-bucket approach)
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 15:14 ` Tom Zanussi
1 sibling, 0 replies; 4+ messages in thread
From: Tom Zanussi @ 2012-10-17 15:14 UTC (permalink / raw)
To: Tim O'Callaghan; +Cc: yocto@yoctoproject.org
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to avoid re-creating a recipe (+my meta-bucket approach)
2012-10-17 8:49 ` Paul Eggleton
@ 2012-10-17 18:09 ` Philip Balister
0 siblings, 0 replies; 4+ messages in thread
From: Philip Balister @ 2012-10-17 18:09 UTC (permalink / raw)
To: Paul Eggleton; +Cc: yocto
On 10/17/2012 01:49 AM, Paul Eggleton wrote:
> 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.
This is an excellent idea!
Philip
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-10-17 18:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.