All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] ANGSTROM_MODE -> SYSTYPE
Date: Sat, 15 Dec 2007 11:49:12 +0100	[thread overview]
Message-ID: <4763B128.6050806@student.utwente.nl> (raw)
In-Reply-To: <164348748.20071215043923@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Sokolovsky schreef:
> 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."

How will a user know if that flag is supported for the distro he/she
wants to use?
should we enhance insane.bbclass to crosscheck TARGET_OS with
SYSTYPE_FOO for the uclibc vs glibc case? And if so, how would it check
between glibc and eglibc?
Having an *easier* OE-blessed way for switching C library would be nice,
but let's make sure people don't shoot themselves in the foot by setting
SYSTYPE_FOO with a distro that has no knowledge of it.

regards,

Koen


>   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).
> 
> 


- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHY7EoMkyGM64RGpERAh1uAJ9/QUGnhZ+4/zKUeOZSgIgMNyuwUACfYb3a
gy3s4p4svQ8M8rbFxThH+9I=
=3c7/
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2007-12-15 10:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-15  2:39 [RFC] ANGSTROM_MODE -> SYSTYPE Paul Sokolovsky
2007-12-15  3:17 ` Khem Raj
2007-12-15 10:49 ` Koen Kooi [this message]
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=4763B128.6050806@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --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.