From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] client/server policy for ebuilds
Date: Thu, 15 Jun 2006 01:29:03 -0400 [thread overview]
Message-ID: <200606150129.04201.vapier@gentoo.org> (raw)
In-Reply-To: <1150114999.5296.0.camel@cgianelloni.nuvox.net>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
On Monday 12 June 2006 08:23, Chris Gianelloni wrote:
> On Sat, 2006-06-10 at 19:56 -0400, Mike Frysinger wrote:
> > On Saturday 10 June 2006 10:29, Chris Gianelloni wrote:
> > > On Fri, 2006-06-09 at 18:34 -0400, Mike Frysinger wrote:
> > > > On Friday 09 June 2006 16:35, Chris Gianelloni wrote:
> > > > > This is the "official" (hehe) request for comments on making a
> > > > > policy of how to handle ebuilds than can be used for either client
> > > > > or server and how to allow for building client-only.
> > > >
> > > > rather than moving to some sort of policy that satisfies no one
> > > > completely and we'll have to back out of later, why dont we wait
> > > > until portage can give us proper support for USE=client/server
> > >
> > > Got an ETA?
> > >
> > > The situation we have now is confusing, at best, to our users, and
> > > something really should be done to resolve it.
> >
> > sure, dont add support for the flags at all at this point, problem solved
>
> You apparently missed that there already are packages in the tree using
> these flags, as well as minimal.
not really ... i'm fully aware of USE=server since ive used it myself
USE=client however doesnt exist, so you'd be incorrect there
> This inconsistent usage is what I was trying to solve in the first
> place.
with a stop gap measure ... i dont think this stop gap effort is worth the
extra time, especially since it'll be simply backed out of down the road
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
prev parent reply other threads:[~2006-06-15 5:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 20:35 [gentoo-dev] [RFC] client/server policy for ebuilds Chris Gianelloni
2006-06-09 21:05 ` Stuart Herbert
2006-06-09 21:21 ` Chris Gianelloni
2006-06-09 23:14 ` Stuart Herbert
2006-06-10 9:51 ` Luis Francisco Araujo
2006-06-09 22:19 ` Ned Ludd
2006-06-09 23:03 ` Henrik Brix Andersen
2006-06-09 22:34 ` Mike Frysinger
2006-06-10 0:24 ` Roy Marples
2006-06-10 0:33 ` Alec Warner
2006-06-10 1:01 ` Roy Marples
2006-06-10 1:27 ` Ned Ludd
2006-06-10 9:43 ` Mike Frysinger
2006-06-10 8:32 ` Kevin F. Quinn
2006-06-10 9:30 ` Roy Marples
2006-06-10 9:44 ` Mike Frysinger
2006-06-10 10:31 ` Kevin F. Quinn
2006-06-10 0:36 ` Stuart Herbert
2006-06-10 14:32 ` Chris Gianelloni
2006-06-10 0:39 ` Luca Barbato
2006-06-10 14:29 ` Chris Gianelloni
2006-06-10 23:56 ` Mike Frysinger
2006-06-12 12:23 ` Chris Gianelloni
2006-06-15 5:29 ` Mike Frysinger [this message]
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=200606150129.04201.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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