From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Naming of packages for x86 archs
Date: Fri, 25 Jul 2008 15:27:31 +0100 [thread overview]
Message-ID: <1216996051.22069.99.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <200807251453.21851.openembedded@haerwu.biz>
On Fri, 2008-07-25 at 14:53 +0200, Marcin Juszkiewicz wrote:
> I would like to start discussion about naming for x86 package archs. One
> of propositions in past was use something like "tune-prescott" does -
> adding description after arch name (i686p4c). This way we can have list
> like:
>
> i586 - pentium
> i586mmx - pentium with mmx, Geode GX1
> i586c3 - VIA C3
> i586k6 - AMD K6
> i586k62 - AMD K6-2, Geode LX
> i586geode - Geode LX with gcc 4.3 or patched 4.2
I'm not totally thrilled with the idea of jamming the tune flags into
the architecture name. This seems like it will give you an explosion of
new arch names which, for 99% of packages, will not be usefully
different to one another.
If any particular distro needs that level of distinction then fine, let
them go it for their packages. But I don't think it should necessarily
be the default.
p.
prev parent reply other threads:[~2008-07-25 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 12:53 [RFC] Naming of packages for x86 archs Marcin Juszkiewicz
2008-07-25 13:17 ` Thomas Kunze
2008-07-25 14:27 ` Phil Blundell [this message]
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=1216996051.22069.99.camel@mill.internal.reciva.com \
--to=pb@reciva.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.