From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: remove boost-jam-native 3.1.11
Date: Thu, 04 Dec 2008 20:31:27 +0100 [thread overview]
Message-ID: <gh9b6f$jbk$1@ger.gmane.org> (raw)
In-Reply-To: <49382D2D.1030504@gmx.net>
On 04-12-08 20:19, Robert Schuster wrote:
> Hi,
> I would like to remove the boost-jam-native recipe for version 3.1.11
> and instead rely on version 3.1.16 which we also have.
Can't we but those recipes (and associated patches) in obsolete/boost/?
That way it will be outside of the default BBPATH and within reach for
people needing/wanting it.
I'm not a big fan deletionist behaviour since we can't tell if people
are relying on it since not everyone keeps their stuff in OE[1].
Also: what happened to removal.txt?
regards,
Koen
[1] OTOH, keeping their stuff out of OE is their own choice, with the
associated troubles, much like external kernel modules and mainline
next prev parent reply other threads:[~2008-12-04 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 19:19 RFC: remove boost-jam-native 3.1.11 Robert Schuster
2008-12-04 19:31 ` Koen Kooi [this message]
2008-12-04 20:58 ` Philip Balister
2008-12-05 11:19 ` Robert Schuster
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='gh9b6f$jbk$1@ger.gmane.org' \
--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.