From: "Jeremy Lainé" <jeremy.laine@bolloretelecom.eu>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE.dev roadworks notification
Date: Tue, 19 Feb 2008 13:07:06 +0100 [thread overview]
Message-ID: <47BAC66A.8090700@bolloretelecom.eu> (raw)
In-Reply-To: <20080219113024.32ba3368@cimmeria>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> My feeling is opt-out. That way you have to read the docs to get
> out and that means you have to understand why you are swimming
> upstream.
>
> One of the most common problems in OE for beginners seems to be
> building packages that conflict in staging. Having the no breaking
> system be the default would be the best.
I would also prefer to see packaged staging as the default.
It will go a long way towards making builds deterministic as
opposed to the current situation where you may or may not
have cruft leftover in your staging directory, depending on
what you built in the past.
- --
Jeremy LAINE
Bolloré telecom | 11bis, rue Scribe | F-75009 Paris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHusZpCL1n3lVB9EYRApO1AJ4lgLwI5o9dVhYEgDMTAtiYv8UJJwCcCuF2
Bo2NZKJ5CNw/9TdCaIanuUQ=
=8yhs
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-02-19 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 11:14 OE.dev roadworks notification Richard Purdie
2008-02-19 11:30 ` Graeme Gregory
2008-02-19 12:07 ` Jeremy Lainé [this message]
2008-02-20 22:37 ` Leon Woestenberg
2008-02-21 9:57 ` Koen Kooi
2008-02-25 21:05 ` Leon Woestenberg
2008-02-20 3:12 ` Junqian Gordon Xu
2008-02-20 3:14 ` Junqian Gordon Xu
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=47BAC66A.8090700@bolloretelecom.eu \
--to=jeremy.laine@bolloretelecom.eu \
--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.