From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/4] distcc: make distccmon-gnome optional and default to off
Date: Tue, 15 Nov 2011 10:51:33 +0000 [thread overview]
Message-ID: <1321354293.26881.157.camel@ted> (raw)
In-Reply-To: <1321346828.1013.23.camel@mattotaupa>
On Tue, 2011-11-15 at 09:47 +0100, Paul Menzel wrote:
> Am Montag, den 14.11.2011, 21:48 +0000 schrieb Richard Purdie:
> > On Mon, 2011-11-14 at 21:55 +0100, Koen Kooi wrote:
> > > Op 14 nov. 2011, om 21:39 heeft Richard Purdie het volgende geschreven:
> > > > On Mon, 2011-11-14 at 20:17 +0100, Koen Kooi wrote:
> > > >> I think splitting distccmon-gnome into a seperate recipe is a better idea.
> > > >
> > > > I think that makes sense in some cases but I'd hate for it to become the
> > > > default approach for issues like this as the duplication of code,
> > > > parsing and build time etc. grate on me. Do we really need separate
> > > > recipes?
> > >
> > > I think for this case, yes. And I'll happily trade needing extra
> > > buildtime for not needing USEFLAGS.
> > >
> > The proposals for alternative recipes for the different combinations got
> > voted down and PACKAGECONFIG was the preferred solution.
>
> Where is this vote (and discussion) documented? I found nothing in the
> OE Wiki and searching for it with »openembedded packageconfig vote
> oe-core list« brought up only some minutes [1].
>
> I also do not remember anything on openembedded-devel where such general
> discussion definitely belong in my opinion.
>
> It would be great if somebody could help me by giving me an URL.
The reference I could find was:
http://lists.linuxtogo.org/pipermail/tsc/2011-October/000302.html
which asked for objections amongst the TSC members, non were received.
I'm drawing a blank finding the previous discussion, I think there was a
different term used and I can't think what it was which makes searching
hard. There was also discussion of the actual patches on the mailing
list (which IMO is where the discussion should really happen).
Cheers,
Richard
next prev parent reply other threads:[~2011-11-15 10:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 18:54 [PATCH 0/4] Remove dependency on X11 when building for qemu machines Paul Eggleton
2011-11-14 18:54 ` [PATCH 1/4] oprofileui: split server to separate recipe to avoid X11 dependency Paul Eggleton
2011-11-14 18:54 ` [PATCH 2/4] qemu-config: split out anjuta-remote-run Paul Eggleton
2011-11-14 18:54 ` [PATCH 3/4] distcc: make distccmon-gnome optional and default to off Paul Eggleton
2011-11-14 19:17 ` Koen Kooi
2011-11-14 20:39 ` Richard Purdie
2011-11-14 20:55 ` Koen Kooi
2011-11-14 21:48 ` Richard Purdie
2011-11-15 7:58 ` Koen Kooi
2011-11-15 10:15 ` Richard Purdie
2011-11-15 11:44 ` Paul Eggleton
2011-11-15 12:15 ` Koen Kooi
2011-11-15 13:43 ` Richard Purdie
2011-11-15 13:59 ` Koen Kooi
2011-11-15 14:42 ` Richard Purdie
2011-11-15 14:55 ` Koen Kooi
2011-11-15 15:12 ` Richard Purdie
2011-11-15 15:23 ` Koen Kooi
2011-11-15 15:27 ` Paul Eggleton
2011-11-15 15:24 ` Paul Eggleton
2011-11-15 8:47 ` Paul Menzel
2011-11-15 10:51 ` Richard Purdie [this message]
2011-11-14 21:56 ` Paul Eggleton
2011-11-14 18:54 ` [PATCH 4/4] qemu-config: update DESCRIPTION and LICENSE Paul Eggleton
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=1321354293.26881.157.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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