From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16738 invoked by uid 1002); 4 Nov 2003 18:10:37 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 21262 invoked from network); 4 Nov 2003 18:10:36 -0000 Date: Tue, 4 Nov 2003 10:10:34 -0800 From: Bob Miller To: gentoo-dev@gentoo.org Message-ID: <20031104181034.GB9610@jogger-egg.com> Mail-Followup-To: gentoo-dev@gentoo.org References: <20031104002017.71d91fc0.genone@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031104002017.71d91fc0.genone@gentoo.org> Organization: Unlikely User-Agent: Mutt/1.5.4i Subject: Re: [gentoo-dev] [IMPORTANT] server/client USE flags X-Archives-Salt: 2f69383d-afd4-4518-9305-82db1603064c X-Archives-Hash: 3ef0df25f811fba558e75ad915ba02f3 Marius Mauch wrote: > 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. Two objections. 1. USE flags are global for the host. "Serverness" is per-service, not per-host. The host that is an apache server may be a mysql client. 2. Overridden USE flags get blown away by updates. A given package is installed once, then upgraded numerous times over the life of a system. It shouldn't need manual intervention every time. I think Jason's idea, having package-local USE flags like samba-server, ntp-client, etc. might make better sense. The portage gods could generalize this so that USE flags have scope and you could define something like USE="-server server:net-fs/samba" for a desktop with shared filesystems. (actual syntax TBD) That would be package-specific and persistent. -- Bob Miller K kbobsoft software consulting http://kbobsoft.com kbob@jogger-egg.com -- gentoo-dev@gentoo.org mailing list