Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: George Shapovalov <george@g.o>
Subject: Re: client+server packages - build which one?
Date: Fri, 09 Jun 2006 15:55:31 +0200
п'ятниця, 9. червень 2006 15:10, Roy Marples Ви написали:
> Some packages provide both a client and a server. As such, users usually
> only want one or the other - and rarely both.
[skip]
> USE client server
> client - just build the client - duh
> server - just build the server - duh
> client and server OR neither then build both.
The problem with this approach is when you have dependencies on a particular 
client or server. Then you cannot sipy depend on a package (with present 
portage) and instead you need to do a hackery detection and bail out in 
pkg_setup. I think this is the reason why, for example, bind comes as two 
packages: bind (for everything) and bind-tools.

Of course this multiplies the number of packages to support, if such situation 
is common. However the solution you describe can be considered "clean" only 
after #2272 is finally resolved..
https://bugs.gentoo.org/show_bug.cgi?id=2272

George

-- 
gentoo-dev@g.o mailing list


References:
client+server packages - build which one?
-- Roy Marples
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
client+server packages - build which one?
Next by thread:
Re: client+server packages - build which one?
Previous by date:
Re: What is "official"?
Next by date:
Re: client+server packages - build which one?


Updated Jun 17, 2009

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.