From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] recipes/images/${distro}
Date: Sat, 27 Feb 2010 18:38:14 +0100 [thread overview]
Message-ID: <20100227173814.GI3206@jama> (raw)
In-Reply-To: <ac9c93b11002270921rb738980ye29c6fd93913107a@mail.gmail.com>
On Sat, Feb 27, 2010 at 06:21:58PM +0100, Frans Meulenbroeks wrote:
> 2010/2/27 Graeme Gregory <dp@xora.org.uk>:
> > On Sat, Feb 27, 2010 at 04:25:27PM +0100, Frans Meulenbroeks wrote:
> >> Dear all,
> One could do:
> BBFILES = "${OE}/org.openembedded.dev/recipes/*/${DISTRO}/*.bb"
> BBFILES += "${OE}/org.openembedded.dev/recipes/*/*.bb"
images directory doesn't look so messy to me as some other directories
and also image recipes are usually quite easy to read/understand, so
I'm not sure why they need to be moved.
> > The other option, angstrom images used to be in recipes/angstrom and we
> > were asked to move them out so other distros can use them. Id be quite
> > happy with them to return to angstrom/ as it seems they are not useful
> > to other distros anyway.
>
> (and on a personal note: maybe 25+ angstrom recipes is a little bit
> overkill, are these all actually used? )
even 25+ images seems more usefull to me than ie 19 mesa recipes and 17x
pixman (I already moved few and all libpixman to obsolete).
So from my point of view, image recipes doesn't need so much maintenance
as just pulls some subset of packages, why should someone remove them?
On the other side, additional patches are usually added only to latest,
most used recipe (where they are usually also tested) and older recipes
are just getting dust.
Hmm I'm already a bit off-topic, but nobody replied to my "Policy for moving
older versions to obsolete" :/.
Regards,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next prev parent reply other threads:[~2010-02-27 17:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 15:25 [RFC] recipes/images/${distro} Frans Meulenbroeks
2010-02-27 16:38 ` Marco Cavallini
2010-02-27 16:56 ` Graeme Gregory
2010-02-27 17:21 ` Frans Meulenbroeks
2010-02-27 17:38 ` Martin Jansa [this message]
2010-02-27 18:04 ` Marcin Juszkiewicz
2010-02-27 18:40 ` Frans Meulenbroeks
2010-02-27 18:45 ` Marcin Juszkiewicz
2010-02-27 19:01 ` Frans Meulenbroeks
2010-02-27 20:11 ` Michael 'Mickey' Lauer
2010-03-03 13:03 ` Otavio Salvador
2010-02-27 20:46 ` Phil Blundell
2010-02-27 21:27 ` Tom Rini
2010-02-28 20:09 ` Koen Kooi
2010-02-28 20:29 ` Frans Meulenbroeks
2010-03-01 16:05 ` Tom Rini
2010-03-01 16:42 ` Philip Balister
2010-02-28 3:34 ` Graeme Gregory
2010-02-28 4:04 ` Tom Rini
2010-02-28 9:46 ` Frans Meulenbroeks
2010-03-01 20:53 ` Richard Purdie
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=20100227173814.GI3206@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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 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.