1 |
Hi Chris, |
2 |
|
3 |
On 6/9/06, Chris Gianelloni <wolf31o2@g.o> wrote: |
4 |
> > > This means if the client and the |
5 |
> > > server for a particular package is in a single package, we should build |
6 |
> > > both by default. |
7 |
> > |
8 |
> > No thanks. That doesn't match the standard operating procedure |
9 |
> > mentioned above. By default, why don't we just build whatever |
10 |
> > $UPSTREAM intended built by default? |
11 |
> |
12 |
> That is *exactly* what I said. |
13 |
|
14 |
Sorry, that's not how I read it. I read you saying that, if $UPSTREAM |
15 |
ship both server/client in a single package, we should build both. I |
16 |
didn't grok that as being the same as building whatever $UPSTREAM |
17 |
indented being built by default. |
18 |
|
19 |
For example, let's say package 'foo' has both client and server code |
20 |
in the one package, but running ./configure w/ no parameters only |
21 |
enables the client. This is the behaviour I believe we should be |
22 |
following. From what you said in your initial email, I understood |
23 |
that you'd like to see both server and client enabled, regardless of |
24 |
what running ./configure w/ no parameters would enable. |
25 |
|
26 |
Seems to be a mis-communication here. |
27 |
|
28 |
> > How will you support building the server-only portions of the package? |
29 |
> I honestly never bothered to consider it, and really don't care. |
30 |
|
31 |
I'm sorry to hear that :( |
32 |
|
33 |
> Someone else can come up with that idea. The problem with using two USE |
34 |
> flags is what do you do when someone chooses neither? |
35 |
|
36 |
This is easily solved by the IUSE requested functionality for Portage, |
37 |
so that each ebuild can propose a default set of USE flags. If the |
38 |
user ends up switching off all required USE flags, this should be |
39 |
detected, and the emerge should refuse to proceed. (Why? Because |
40 |
otherwise USE-based DEPs can't work deterministically). |
41 |
|
42 |
Ciaran filed a bug about what we'd need a year or so back. |
43 |
|
44 |
Best regards, |
45 |
Stu |
46 |
-- |
47 |
gentoo-dev@g.o mailing list |