From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Renamed: Generic distro
Date: Mon, 28 Jan 2008 13:59:42 -0500 [thread overview]
Message-ID: <479E261E.1010903@balister.org> (raw)
In-Reply-To: <479E2053.6090902@student.utwente.nl>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Koen Kooi wrote:
> Besides not being named 'generic', what are the arguments against making
> angstrom the 'generic' distro in OE? It's the closest thing of showing
> off all features of OE *and* doing it the OE-way.
At the risk of putting words in to Mickey's mouth, my view a generic
distro is a generic.conf that contains the absolute minimum number of
lines required to build an image successfully. Maybe we could call it
minimal distro and remove generic?
Angstrom has features, generic does not.
The key is not to define the generic distro clearly and not let it
feature creap towards Angstrom. (Kind of like minimal-image trying to
get less minimal based on peoples viewpoint of what a minimal-image is)
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-01-28 18:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 9:04 [oe-commits] org.oe.dev gnuplot: update 4.2.2, add 4.3.0+cvs Koen Kooi
2008-01-28 11:52 ` Junqian Gordon Xu
2008-01-28 12:48 ` Paul Sokolovsky
2008-01-28 15:20 ` pHilipp Zabel
2008-01-28 18:03 ` Paul Sokolovsky
2008-01-28 15:40 ` Graeme Gregory
2008-01-28 17:28 ` Michael 'Mickey' Lauer
2008-01-28 18:34 ` Koen Kooi
2008-01-28 18:52 ` Michael 'Mickey' Lauer
2008-01-28 18:59 ` Philip Balister [this message]
2008-01-28 19:21 ` Renamed: Generic distro Michael 'Mickey' Lauer
2008-01-28 19:18 ` [oe-commits] org.oe.dev gnuplot: update 4.2.2, add 4.3.0+cvs Paul Sokolovsky
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=479E261E.1010903@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.