From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] client+server packages - build which one?
Date: Fri, 09 Jun 2006 14:49:16 -0400 [thread overview]
Message-ID: <1149878957.22473.73.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <200606091410.51183.uberlord@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
On Fri, 2006-06-09 at 14:10 +0100, Roy Marples wrote:
> Some packages provide both a client and a server. As such, users usually only
> want one or the other - and rarely both.
>
> A good candidate is net-misc/dhcp as it installs a DHCP client and server.
> Which makes no sense really, so I'd like to put some USE flags here to show
> what I want, or not want to build.
>
> A quick scan through the use flags show no real consistency, so here's what I
> propose
>
> USE client server
> client - just build the client - duh
> server - just build the server - duh
> client and server OR neither then build both.
>
> Other packages to possably beneift
> udhcp
> mldonkey
> samhain
> bacula
> boxbackup
>
> Interestingly, many packages have a server USE flag but not a client one -
> maybe make both a global USE flag?
>
> Good idea? Bad idea? Thoughts?
(Yeah, I know, repeating our IRC conversation.)
Bug #12499
The truth is that we don't ever want to become like the binary
distributions. We don't want to have to have separate
client/server/common/devel as it removes many of the advantages that
Gentoo has. The default should *always* be to install the package as it
was intended from upstream, completely intact. Now, it has started to
become a practice to have a "minimal" USE flag on certain packages that
reduces the functionality to the bare client portion. I see no real
problem with this, so long as the default is to always build/install the
full package.
That's my $0.02 on the matter.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-09 18:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 13:10 [gentoo-dev] client+server packages - build which one? Roy Marples
2006-06-09 13:55 ` George Shapovalov
2006-06-09 13:57 ` Alec Warner
2006-06-09 14:31 ` Patrick McLean
2006-06-09 17:15 ` Luca Barbato
2006-06-09 16:43 ` Roy Marples
2006-06-09 19:04 ` Chris Gianelloni
2006-06-09 19:13 ` Donnie Berkholz
2006-06-09 19:27 ` Roy Marples
2006-06-09 20:22 ` Mike Frysinger
2006-06-09 21:14 ` Chris Gianelloni
2006-06-09 18:49 ` Chris Gianelloni [this message]
2006-06-09 18:58 ` Donnie Berkholz
2006-06-09 18:52 ` Kevin F. Quinn
[not found] ` <20060808085657.GA15665@nibiru.local>
2006-08-08 10:11 ` Roy Marples
2006-08-08 10:24 ` Brian Harring
2006-08-08 10:55 ` Enrico Weigelt
2006-08-08 11:10 ` Brian Harring
2006-08-08 14:46 ` Enrico Weigelt
2006-08-08 15:06 ` Thomas Cort
2006-08-08 17:46 ` Joshua Nichols
2006-08-08 11:48 ` Simon Stelling
2006-08-08 18:50 ` Colin Kingsley
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=1149878957.22473.73.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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