1 |
On Wed, 4 Mar 2009 02:32:13 -0500 |
2 |
Caleb Cushing <xenoterracide@×××××.com> wrote: |
3 |
|
4 |
> I'd like to start with, I'm not trying to stir up trouble but since |
5 |
> questions were asked i'll answer them. |
6 |
> |
7 |
> > If you think neither should exist why do you have an opinion about |
8 |
> > this at all? |
9 |
> |
10 |
> I merged the java-overlay into regen2 a couple of weeks ago. as of |
11 |
> right now I've no plans to support java-experimental. |
12 |
|
13 |
Then don't. Really. |
14 |
|
15 |
> I filed a bug on xorg-server |
16 |
> 1.6.0 not being in tree. It was resolved fixed (in overlay) (which |
17 |
> another bug clearly states it has amd64 build issues). since when has |
18 |
> (in overlay) been an acceptable solution to a missing package? |
19 |
|
20 |
|
21 |
That's pretty much at developer discretion. Please note that we have to |
22 |
have an actual working distribution, which means that sometimes we use |
23 |
overlays to make basic QA checks against installed packages (Does it |
24 |
build? Does it work?). That said, I try to not close bugs before |
25 |
they've been resolved in-tree precisely because of the reaction that |
26 |
provoked on bug 260582. I personally like to have my bugs reflect the |
27 |
state of the tree. |
28 |
|
29 |
Bugzilla is a tool for developers to track progress, not for |
30 |
third-party distributions to track progress. You've forked the tree. |
31 |
That's fine. The license allows that. But it doesn't obligate us to |
32 |
adapt our tools to fit your purpose. Bugzilla is a strictly |
33 |
technical tool, so comments on bugs should be kept free of ad hominem |
34 |
remarks. From all parties. |
35 |
|
36 |
Your behavior on bug 260582 was clearly unacceptable. You |
37 |
seem to think that we owe you something. Please re-examine your |
38 |
premises. Donnie already told you he was working on it. Our job is not |
39 |
to support your distribution. It is to make the best distro for |
40 |
ourselves. In the case of xorg-server, that means getting something |
41 |
into the tree that works. A masked ebuild will in this case be more |
42 |
bother than it's worth because the mask would have to encompass a |
43 |
bunch of other packages. Which leads me on to the next paragraph... |
44 |
|
45 |
> I said it before, the reason I like gentoo* distro's is I don't have |
46 |
> to find the repository to get the latest package, that's just a pain, |
47 |
> in ubuntu, in opensuse, in fedora... etc. But no more... officially |
48 |
> supported huge overlays have ruined this. |
49 |
|
50 |
Please contact me on IRC. I'll mentor you. It shouldn't be painful for |
51 |
someone as knowledgeable as you. That way you get to fix most problems |
52 |
yourself. If you prefer someone else to mentor you, we can probably |
53 |
arrange that too. |
54 |
|
55 |
> on the topic of sunrise, I approve of sunrise to a degree. I like the |
56 |
> non-reviewed half, but once they're reviewed they should be put in |
57 |
> tree. Isn't it true that some of those packages never get maintainers? |
58 |
|
59 |
They need maintainers to be maintained in-tree. Sorry, but that's the |
60 |
deal. |
61 |
|
62 |
> users don't know how to hack. the very definition of user says that, |
63 |
> imo. There are developers, admins, and users. admins don't want |
64 |
> overlays, they are supposed to be unstable. users can't hack, so what |
65 |
> do they care. the problem is, an overlay has become a repo, I'm not |
66 |
> sure that it was originally intended for that. |
67 |
|
68 |
It wasn't. And if an admin has a problem with overlays he can become a |
69 |
developer. *hint* |
70 |
|
71 |
There are too many possible packages for the number of developers we |
72 |
have in Gentoo. But that'll always be the case, probably, no matter how |
73 |
many developers you pour in. If you have specific grievances, the |
74 |
recruitment process is the obvious remedy since you seem to have the |
75 |
time, the ability and the will to adress them. |
76 |
|
77 |
> this does not mean officially supported overlays. You obviously won't |
78 |
> commit just anything to an officially supported overlay which suggests |
79 |
> that you don't allow 'mucking around'. |
80 |
|
81 |
The only thing in Gentoo that's 'officially supported' is the tree. |
82 |
|
83 |
> > Further, overlays are good places to put ebuilds for software that |
84 |
> > is more experimental than what's expected for ~arch. That includes |
85 |
> > live ebuilds. In the end, overlays have a (far) lower level of |
86 |
> > guaranteed quality than the main tree, for their ebuilds |
87 |
> |
88 |
> because ~arch is supposed to work? take open bug on wine-1.1.16 it |
89 |
> doesn't build on amd64 and yet it's ~amd64. |
90 |
|
91 |
QA fail, amd64 keyword dropped. |
92 |
|
93 |
> how about that nam ebuild |
94 |
> that has invalid bash that I mentioned? that's some quality work |
95 |
> there. The point is the tree is no better or worse than the overlays |
96 |
> in many cases. |
97 |
|
98 |
In many cases that's true, but on average, the QA of the tree is much |
99 |
better than overlays. |
100 |
|
101 |
> perhaps this is the real problem gentoo's primary way to accept user |
102 |
> contributions is via overlays. I disagree with the calling of Funtoo |
103 |
> as one big overlay, it's a replacement tree, and it provides |
104 |
> everything needed within that tree, as does regen2. |
105 |
|
106 |
We Need Git. It would really ease the workflow of accepting user |
107 |
contributions if users could just set up their own overlay and sent me |
108 |
an email asking to merge their changesets. |
109 |
|
110 |
> overlays however |
111 |
> rely on an external tree, and now you've been discussing making them |
112 |
> rely on other overlays. |
113 |
|
114 |
Personally, I think that any itch that's scratch-worthy is commendable |
115 |
but I would personally abstain from the rather elaborate java overlay |
116 |
setup. Not because it doesn't work, it does to a degree, but because it |
117 |
keeps potential developers away from Gentoo, instead playing in |
118 |
sandboxes. And because it's a pain in the neck to keep track of |
119 |
packages that aren't being used. |
120 |
|
121 |
> Regen2, is attempting to fix these problems, and more. I do try to get |
122 |
> my fixes back upstream here, but more often than not the bug |
123 |
> languishes. I don't think Gentoo is bad, but I do think it's taken a |
124 |
> wrong turn. But I suppose that these things are problems are simply my |
125 |
> opinion. |
126 |
|
127 |
We need to get you recruited. Why haven't you pushed us more? You could |
128 |
have made thousands of commits already, fixing a substantial amount of |
129 |
the problems you've raised. I know the perl herd is always in need of |
130 |
new devs. This isn't a quick fix. You'll have to work with people and |
131 |
that can sometimes be frustrating. But you'll get to be part of the |
132 |
development process and you'll get to work with the things you care |
133 |
about. |
134 |
|
135 |
> I've probably already offended a large share of people on this list, |
136 |
> now lets see if I can offend a few more by soliciting. |
137 |
|
138 |
If people can't take a bit of honest criticism, we've become too |
139 |
thin-skinned. |
140 |
|
141 |
/loki_val |