1 |
On Thu, Feb 2, 2017 at 11:25 AM, Michael Orlitzky <mjo@g.o> wrote: |
2 |
> |
3 |
> If (base == minimal), then all of the upstream defaults need to be added |
4 |
> to package.use for the upstream-defaults profile. That's bad, |
5 |
|
6 |
I'll go further and say that it is unacceptably bad. |
7 |
|
8 |
> but if |
9 |
> (base == upstream-defaults), then the important IUSE defaults need to be |
10 |
> copy/pasted from our ebuilds into the minimal profile. The latter is |
11 |
> more spiritually damning =) |
12 |
> |
13 |
|
14 |
So, I'll admit I've never been one that cared a great deal about |
15 |
minimalism so I appreciate that I may not be the best one to judge |
16 |
this, so let's go ahead and embrace your statement for the purpose of |
17 |
debate. |
18 |
|
19 |
Is there a better way we can have our cake and eat it too? I'll admit |
20 |
that a huge package.use on the minimal profile isn't a whole lot |
21 |
better than a huge package.use on all the other profiles. |
22 |
|
23 |
Do we need another form of syntax in individual ebuilds to try to |
24 |
separate out the various cases you cite? Does anybody care to |
25 |
actually suggest one? |
26 |
|
27 |
I still think that we shouldn't encourage users to lightly deviate |
28 |
from all the upstream defaults. There are of course legitimate |
29 |
reasons for doing so, and you and I can probably appreciate when we |
30 |
should do this, but for somebody starting out we're giving them a lot |
31 |
of rope to hang themselves with. It is like building a kernel |
32 |
answering no to the largest number of questions possible while still |
33 |
actually building something. I'd actually be curious as to what that |
34 |
kernel would even be capable of doing (there are a lot of fairly |
35 |
essential things you can turn off in the kernel). |
36 |
|
37 |
In the same way, we shouldn't be too quick to deviate from upstream |
38 |
defaults ourselves (#4 in your example), beyond actual integration |
39 |
work. |
40 |
|
41 |
I'll admit the current state is a bit of a compromise, but I don't |
42 |
think we should change it unless we're changing it to something |
43 |
significantly better. This is a pretty big-impact change. |
44 |
|
45 |
-- |
46 |
Rich |