public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] client+server packages - build which one?
Date: Tue, 8 Aug 2006 12:55:28 +0200	[thread overview]
Message-ID: <20060808105527.GE15665@nibiru.local> (raw)
In-Reply-To: <200608081111.59602.uberlord@gentoo.org>

* Roy Marples <uberlord@gentoo.org> schrieb:
> On Tuesday 08 August 2006 09:56, Enrico Weigelt wrote:
> > If you want an dhcp client, install "dhcp-client", if you
> > want an dhcp server, install "dhcp-server". Could it be simpler ?
> 
> Maybe you missed the part of the discussion where we thought that 
> maintaing 3 ebuilds vs 1 ebuild was a bad idea. Yes we would need 
> 3 due to the way that the dhcp builds and installs.

Okay, but they're maintained at the same time. 

Let's see where the extra work could come from: 

+ changes in build options. okay, have to type some things twice.
  adds 5mins
+ three packages have to be tested now. today one package has to 
  be tested in three variants. is there really more work ?

The 3rd package is mostly copy-and-paste, since doesn't actually
do anything. It's just rdeps based on useflags. Just an multiplexer.

On the other hand I see some more changes on an split:
Let's say, in a newer version, there's an interesting improvement 
in the server, but an bad bug in the client. Currently the client
would block the server, just for buerocrativ reasons.
After a split, both part-packages can evolve separately.

<snip> 

> The minimal flag currently controls this anyway - you always get 
> the client but the server is optional. 

But it's very unclear. Ask around in the user list, who knows what 
"minimal" in this special case means (without extra reading the 
documentation). Such useflags should be obvious, but "minimal" isnt.


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-08-08 11:02 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
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 [this message]
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=20060808105527.GE15665@nibiru.local \
    --to=weigelt@metux.de \
    --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