public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Troy Dack <troy@tkdack.com>
To: "gentoo-dev@gentoo.org" <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] [IMPORTANT] server/client USE flags
Date: Tue, 04 Nov 2003 11:03:39 +1100	[thread overview]
Message-ID: <1067904218.5520.5.camel@carbon.internal.lan> (raw)
In-Reply-To: <20031104002017.71d91fc0.genone@gentoo.org>

On Tue, 2003-11-04 at 10:20, Marius Mauch wrote:
> Hi,
> 
> currently we have a lot of packages in the portage tree that provide
> both server and client implementations of a package, big things like
> mysql and samba but also small stuff like telnet-bsd. Often people don't
> need the server part of these packages, but currently there is no way to
> disable them. Some packages have splitted the package, but this is IMO
> not a good idea in general, as often the ebuilds are the same except for
> one or two commands.
> So my idea (as well as others) is to add a new "server" USE flag that
> controls wether the server part of a package is build. This idea is
> outlined in more details on bug 12499, which also had the idea of a
> "client" USE flag, so that it's possible to only build the libs or only
> the server, however I think that such a flag will create more problems
> than benefits (see the bug for explanations).
> So, I'd like to get some opinions/comments from people on this idea, as
> this is coming up about every month and there wasn't really any action
> to solve this issue.
> 
> Marius

I like this idea, it makes sense and seems more logical than a client
USE flag.

I think that a *big fat notice* in /etc/make.conf should be included
just above the USE=... line though, something like:

# If you intend to use this machine as a server and require both
# client/server portions of packages like mysql or samba installed then
# ensure that you include  "server"  in your USE flags below.

Hopefully this will go some way to reducing all the "I emerged samba but
didn't get smbd/nmbd" bugs that are likely to come about.

A GWN or simply a News item as well as a post to gentoo-announce should
be made when this is implemented in the ebuilds.

-- 
Troy Dack					http://linux.tkdack.com
<troy@tkdack.com>				http://webportage.sf.net

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D90BE3C
Key fingerprint = 1F3D 6C15 16AA 09D5 0C96  92E5 FD89 16F9 4D90 BE3C


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-11-04  0:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 23:20 [gentoo-dev] [IMPORTANT] server/client USE flags Marius Mauch
2003-11-03 23:55 ` Andrew Gaffney
2003-11-04  1:17   ` Jason Wever
2003-11-04  5:54     ` Donnie Berkholz
2003-11-03 23:58 ` Philippe Coulonges
2003-11-04  0:03 ` Troy Dack [this message]
2003-11-04  0:17 ` Donny Davies
2003-11-04  0:42   ` Jason Rhinelander
2003-11-04  1:18     ` Marius Mauch
2003-11-04  3:30       ` Matthieu Sozeau
2003-11-04  1:00   ` Marius Mauch
2003-11-04 10:50     ` Mike Williams
2003-11-04 14:38       ` William Hubbs
2003-11-04 19:57       ` [gentoo-dev] Gentoo Rocks My Socks Stroller
2003-11-04  1:04   ` [gentoo-dev] [IMPORTANT] server/client USE flags Luke-Jr
2003-11-04  9:14   ` Matthew Kennedy
2003-11-04 10:48   ` Heiko Vogel
2003-11-04 18:10 ` Bob Miller
2003-11-04 18:23   ` John Davis
2003-11-04 18:37     ` Jon Portnoy
2003-11-04 18:55       ` Donny Davies
2003-11-05  1:24         ` Terje Kvernes
2003-11-05  1:39           ` Luke-Jr
2003-11-05  2:01             ` Chris Smith
2003-11-05  2:33               ` Luke-Jr
2003-11-05  2:23             ` Terje Kvernes
2003-11-05  9:46               ` Paul de Vrieze
2003-11-05 10:03                 ` Patrick Kursawe
2003-11-06  6:37                 ` C. Brewer

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=1067904218.5520.5.camel@carbon.internal.lan \
    --to=troy@tkdack.com \
    --cc=gentoo-dev@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