Gentoo Archives: gentoo-dev

From: Stuart Herbert <stuart.herbert@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] client/server policy for ebuilds
Date: Fri, 09 Jun 2006 21:11:05
Message-Id: b38c6f4c0606091405o7bb99923xa9e5b9a937121189@mail.gmail.com
In Reply to: [gentoo-dev] [RFC] client/server policy for ebuilds by Chris Gianelloni
1 On 6/9/06, Chris Gianelloni <wolf31o2@g.o> wrote:
2 > Gentoo's standard operating procedure is to build packages as they were
3 > intended and packaged from upstream.
4
5 +1
6
7 > This means if the client and the
8 > server for a particular package is in a single package, we should build
9 > both by default.
10
11 No thanks. That doesn't match the standard operating procedure
12 mentioned above. By default, why don't we just build whatever
13 $UPSTREAM intended built by default?
14
15 It means that different packages will behave differently throughout
16 the tree, but that's okay, and is more Gentoo-like than your proposal.
17
18 > To facilitate building the client portions only, the
19 > use of the local "minimal" USE flag is allowed.
20
21 How will you support building the server-only portions of the package?
22 I don't want clients I don't need on my servers. "client" and
23 "server" USE flags would appear to make much more sense here (for
24 packages that have any such clear distinction), and will play better
25 when USE-based DEPs become reality.
26
27 Best regards,
28 Stu
29 --
30 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] [RFC] client/server policy for ebuilds Chris Gianelloni <wolf31o2@g.o>