All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] recipes/images/${distro}
Date: Sat, 27 Feb 2010 19:04:21 +0100	[thread overview]
Message-ID: <201002271904.22479.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <ac9c93b11002270921rb738980ye29c6fd93913107a@mail.gmail.com>

Dnia sobota, 27 lutego 2010 o 18:21:58 Frans Meulenbroeks napisał(a):
> One could do:
> BBFILES = "${OE}/org.openembedded.dev/recipes/*/${DISTRO}/*.bb"
> BBFILES += "${OE}/org.openembedded.dev/recipes/*/*.bb"
 
BBFILES = "${OE}/org.openembedded.dev/recipes/" is supported since I do not 
remember when.

Making extra levels in recipes/ dir was discussed so many times that it makes 
me sad when I see yet another discussion about it which will change nothing.

Images/ directory never had sensible naming. "angstrom-gnome-image" is smaller 
then "angstrom-x-image", x11-image is another version of gpe-image (content is 
other but result is same - user lands in GPE + Matchbox v1). If you want to 
have kind of order there then start creating "frans-really-minimal", "frans-
basic-x11-without-gtk-but-small-as-possible", "frans-x11-gpe-mb1", "frans-x11-
gnome" etc images. 

This directory is dump of recipes created by many developers, some of them are 
probably 5-6 years old. There are many recipes for images outside of our 
repository (like bug-image-production for example or those which generate 1GB 
sized rootfs from Montavista). I have on disk image recipe which generate 
package which I use to generate final image. Etc, ETc, ETC...

So generally I am against moving recipes which mention angstrom to 
recipes/angstrom/ just because they contain 'angstrom' word inside. If I will 
push "umbaumba-magic-image" recipe will you opt for moving it to 
recipes/umbaumba just because I wrote it for my internal-no-one-saw-it-and-
who-knows-does-it-exists-at-all distribution?

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz





  parent reply	other threads:[~2010-02-27 18:08 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
2010-02-27 18:04     ` Marcin Juszkiewicz [this message]
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=201002271904.22479.marcin@juszkiewicz.com.pl \
    --to=marcin@juszkiewicz.com.pl \
    --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.