From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: introducing a new architecture/machine; policy ? (and a question)
Date: Wed, 23 Jun 2010 12:07:18 +0200 [thread overview]
Message-ID: <4C21DCD6.4090509@balister.org> (raw)
In-Reply-To: <20100623110315.16293a95@xora-desktop.xora.org.uk>
On 06/23/2010 12:03 PM, Graeme Gregory wrote:
> On Wed, 23 Jun 2010 11:54:21 +0200
> Frans Meulenbroeks<fransmeulenbroeks@gmail.com> wrote:
>
>> 2010/6/23 Graeme Gregory<dp@xora.org.uk>:
>>>>>> Also I don't feel empowered to make changes in distribution
>>>>>> specific files.
>>>
>>> Why not, chances are Angstrom maintainers would be quite happy for
>>> you to patch angstrom*.conf if you ask us.
>>>
>>> Graeme
>>
>> distribution != angstrom
>> There are more distributions out there.
Right now, toolchain selection is done in distro files not machine
files. I agree this is not the clearest approach, however adding the
toolchain selection to the machine files may have unexpected side effects.
I would ask DISTRO maintainers to add the needed overrides, and explore
alternative methods as a separate effort.
Philip
>>
> I think the other distros are almost as friendly as us :-)
>
> Anyway the sane-* files are free for all with Acks.
>
> Graeme
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2010-06-23 10:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 9:58 introducing a new architecture/machine; policy ? (and a question) Frans Meulenbroeks
2010-06-20 10:10 ` Frans Meulenbroeks
2010-06-20 12:35 ` Koen Kooi
2010-06-20 15:38 ` Frans Meulenbroeks
2010-06-23 8:53 ` Frans Meulenbroeks
2010-06-23 9:24 ` Koen Kooi
2010-06-23 9:36 ` Graeme Gregory
2010-06-23 9:54 ` Frans Meulenbroeks
2010-06-23 10:03 ` Graeme Gregory
2010-06-23 10:07 ` Philip Balister [this message]
2010-06-23 10:32 ` Koen Kooi
2010-06-23 11:16 ` Frans Meulenbroeks
2010-06-23 17:19 ` Khem Raj
2010-06-23 19:55 ` Frans Meulenbroeks
2010-06-23 22:20 ` Khem Raj
2010-06-23 17:15 ` Khem Raj
2010-06-23 17:18 ` Tom Rini
2010-06-23 10:09 ` Frans Meulenbroeks
2010-06-23 10:30 ` Koen Kooi
2010-06-23 17:23 ` Khem Raj
2010-06-23 20:04 ` Frans Meulenbroeks
2010-06-23 21:55 ` Adrian Alonso
2010-06-23 22:16 ` Khem Raj
2010-06-23 22:26 ` Khem Raj
2010-06-24 9:27 ` Koen Kooi
2010-06-24 11:23 ` Frans Meulenbroeks
2010-06-24 15:10 ` Khem Raj
2010-06-20 22:59 ` Khem Raj
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=4C21DCD6.4090509@balister.org \
--to=philip@balister.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox