1 |
On Fri, 2006-06-09 at 14:04 +0200, Stefan Schweizer wrote: |
2 |
> Carsten Lohrke wrote: |
3 |
> > You should at least make it visible in bold letters on the overlay.g.o |
4 |
> > front page, what the conditions of each overlay are and which foo@g.o |
5 |
> > address bugs have to be assigned to. |
6 |
> |
7 |
> |
8 |
> Please, do not assume our users being stupid. They know that they are using |
9 |
> an ebuild from the sunrise overlay with zero support. They deliberately |
10 |
> typed |
11 |
> |
12 |
> "svn co http://overlays.gentoo.org/svn/proj/sunrise/category/application" |
13 |
> "emerge application" |
14 |
|
15 |
Umm... and what if they checkout the entire repository and get something |
16 |
they weren't expecting? |
17 |
|
18 |
I love how you simply just dismiss this possibility as something that |
19 |
either can't happen, or something that won't happen because the users |
20 |
will "know what they're doing" when they use this overlay. |
21 |
|
22 |
> And also there are only applications from maintainer-wanted or |
23 |
> maintainer-needed allowed in the overlay. Because packages are not supposed |
24 |
> to overwrite files from other ebuilds it is unlikely that they can cause |
25 |
> any damage to applications that have not been directly installed from the |
26 |
> overlay. |
27 |
|
28 |
Hahahahahahahahahahahaha!! |
29 |
|
30 |
Oh wait... Are you serious? What if it is a library? What if it is an |
31 |
alternative to a library already in the tree? Hrrrmn... plot thickens. |
32 |
|
33 |
> > Also some warning that an overlay may |
34 |
> > break the tree or fubar the users system |
35 |
> That is not the intention of the overlay. Everyone can help fixing breakage, |
36 |
> it is not like with the current tree, where you have apps broken for a few |
37 |
> days, weeks or even months because the maintainer is unreachable. With |
38 |
> fixes (by users) spread all over bugzilla. |
39 |
|
40 |
Everyone that you happen to include as allowed to actually commit, you |
41 |
mean. As opposed to "everyone that can sign themselves up for |
42 |
bugzilla"? |
43 |
|
44 |
> It is designed to be more open and more easily fixable. |
45 |
|
46 |
Sure. More open then a self-registering system. Gotcha. |
47 |
|
48 |
-- |
49 |
Chris Gianelloni |
50 |
Release Engineering - Strategic Lead |
51 |
x86 Architecture Team |
52 |
Games - Developer |
53 |
Gentoo Linux |