From: Paul Sokolovsky <pmiscml@gmail.com>
To: Openembedded-devel@lists.openembedded.org
Subject: [RFC] ANGSTROM_MODE -> SYSTYPE
Date: Sat, 15 Dec 2007 04:39:23 +0200 [thread overview]
Message-ID: <164348748.20071215043923@gmail.com> (raw)
Hello Openembedded-devel,
ANGSTROM_MODE config variable has proven to be very useful and
successful feature during the Angstrom evolution. IMHO, it is worth
generalization of its meaning and naming to become a generic
additional OE distro configuration parameter. So, I'd like to propose
it to be renamed to SYSTYPE, with the description "Select particular
system variant of a distribution which supports such feature, e.g.,
underlying libc type."
Obviously, it wouldn't be limited to libc type, but intended to be a
generic sub-parameter of a distro, it could be debug/release type,
size type (minimal/standard/extended), whatever. The usage idea is to
have standard name for such generic parameter, plus semantically it
should be expected that a distro allows to build different SYSTYPE's
side-by-side in the same build dir (like Angstrom does for libc
variants).
--
Best regards,
Paul mailto:pmiscml@gmail.com
next reply other threads:[~2007-12-15 2:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 2:39 Paul Sokolovsky [this message]
2007-12-15 3:17 ` [RFC] ANGSTROM_MODE -> SYSTYPE Khem Raj
2007-12-15 10:49 ` Koen Kooi
2007-12-15 15:05 ` Paul Sokolovsky
2007-12-15 13:26 ` Leon Woestenberg
2007-12-15 15:35 ` Paul Sokolovsky
2007-12-16 4:51 ` Rod Whitby
2007-12-16 9:36 ` Paul Sokolovsky
2007-12-20 18:38 ` Leon Woestenberg
2007-12-20 20:10 ` Paul Sokolovsky
2007-12-21 21:42 ` Leon Woestenberg
2007-12-16 20:48 ` Marcin Juszkiewicz
2007-12-16 22:31 ` Paul Sokolovsky
2007-12-16 22:58 ` Richard Purdie
2007-12-17 2:57 ` 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=164348748.20071215043923@gmail.com \
--to=pmiscml@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.