From: Shane Dixon <shane.dixon@atmel.com>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: new stable release
Date: Tue, 17 Mar 2009 17:06:19 +0000 [thread overview]
Message-ID: <1237309579.20770.17.camel@homestead> (raw)
In-Reply-To: <20090317163556.GK26343@smtp.west.cox.net>
On Tue, 2009-03-17 at 09:35 -0700, Tom Rini wrote:
>
> I'd like to add Ubuntu 8.10. Further, for each of these reference host
> configurations we need to say what's installed, preferably by meta
> packages (in Ubuntu's case, say ubuntu-minimal + ubuntu-standard) and
> specific packages ('gcc', 'g++', etc..). And I too can help with the
> env. FWIW, a chroot should be good enough for this..
>
8.04 might be a better target for a "reference machine" because it's an
LTS release (although I personally use 8.10). I think that the goal
should be solid support for the longest (within reason of course) amount
of time. If I intend to write a document for a vendor explaining how to
use OE as a build environment for their code, the intent should be that
I don't have to re-write it again and again over the course of the next
year (Ubuntu releases every 6 months).
I think that one of the greatest reasons for a good solid branch is that
documentation can truly be reliable because we're not aiming at a moving
target.
--
Shane Dixon
Linux Engineer
Atmel Corporation
Office: 719.540.1123
E-mail: shane.dixon@atmel.com
next prev parent reply other threads:[~2009-03-17 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 14:38 RFC: new stable release Marcin Juszkiewicz
2009-03-17 14:50 ` Koen Kooi
2009-03-17 15:15 ` Mathieu Chouinard
2009-03-17 15:23 ` Marcin Juszkiewicz
2009-03-17 15:09 ` Matteo Fortini
2009-03-17 15:25 ` Mike (mwester)
2009-03-17 16:35 ` Tom Rini
2009-03-17 17:06 ` Shane Dixon [this message]
2009-03-17 17:26 ` Tom Rini
2009-03-17 15:39 ` Richard Purdie
2009-03-17 17:42 ` Philip Balister
-- strict thread matches above, loose matches on Subject: below --
2009-03-17 15:04 Marco Cavallini
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=1237309579.20770.17.camel@homestead \
--to=shane.dixon@atmel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox