On Tue, Aug 08, 2006 at 12:55:28PM +0200, Enrico Weigelt wrote: > * Roy Marples 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. To do that, you have to seperate any libs used between the two. In such a pkg, there *should* be a common lib- so you're suggesting either static linkage of said code (disk but more importantly mem bloat), or so renaming (further divergance from upstream, more issues in glsa handling). Yet *more* manual work. You want this, implement it in an overlay. You get what you want, and if you manage to make it not suck the big one, hey, maybe you might convince a few people. Either way, people aren't going to yield- put in the work to prove them wrong rather then just trying to talk them into the ground please. Besides... pushing this hard for something, you better be willing to do the work yourself- can't expect others to do what you want when they disagree. ~harring