| 1 |
Carsten Lohrke wrote: |
| 2 |
> You should at least make it visible in bold letters on the overlay.g.o |
| 3 |
> front page, what the conditions of each overlay are and which foo@g.o |
| 4 |
> address bugs have to be assigned to. |
| 5 |
|
| 6 |
|
| 7 |
Please, do not assume our users being stupid. They know that they are using |
| 8 |
an ebuild from the sunrise overlay with zero support. They deliberately |
| 9 |
typed |
| 10 |
|
| 11 |
"svn co http://overlays.gentoo.org/svn/proj/sunrise/category/application" |
| 12 |
"emerge application" |
| 13 |
|
| 14 |
And also there are only applications from maintainer-wanted or |
| 15 |
maintainer-needed allowed in the overlay. Because packages are not supposed |
| 16 |
to overwrite files from other ebuilds it is unlikely that they can cause |
| 17 |
any damage to applications that have not been directly installed from the |
| 18 |
overlay. |
| 19 |
|
| 20 |
> Also some warning that an overlay may |
| 21 |
> break the tree or fubar the users system |
| 22 |
That is not the intention of the overlay. Everyone can help fixing breakage, |
| 23 |
it is not like with the current tree, where you have apps broken for a few |
| 24 |
days, weeks or even months because the maintainer is unreachable. With |
| 25 |
fixes (by users) spread all over bugzilla. |
| 26 |
It is designed to be more open and more easily fixable. |
| 27 |
|
| 28 |
-Stefan |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives