| 1 |
Chris Bainbridge wrote: |
| 2 |
> On 08/06/06, foser <foser@g.o> wrote: |
| 3 |
>> I don't think the problem with maintainer-wanted ebuilds is that they |
| 4 |
>> are crappy, but that there is no dev willing to maintain them and ensure |
| 5 |
>> their quality over time. 'sunrise' (who came up with that name ? cheap |
| 6 |
>> asian poetry attempt) doesn't change that by adding it to an 'official' |
| 7 |
>> overlay. |
| 8 |
> |
| 9 |
> One of the problems is that developer interest is transitory. The |
| 10 |
> current system suggests that a developer take personal responsibility |
| 11 |
> for ebuilds they maintain, and they maintain them until another |
| 12 |
> developer steps up. It would be nice (and I guess this is one of the |
| 13 |
> aims of sunrise) if there were a way for people to contribute ebuilds |
| 14 |
> that they are interested in at the time, but don't want to promise to |
| 15 |
> maintain forever. Think about wikipedia - how many pages would there |
| 16 |
> be if every page creator had to guarantee that they would maintain |
| 17 |
> each page indefinately? |
| 18 |
> |
| 19 |
> The time it takes to actually apply fixes etc. is another point. |
| 20 |
> Bugzilla is a poor system for sharing and managing the flow of |
| 21 |
> ebuilds and patches. It would be nice if there were a way for non-devs |
| 22 |
> to publish ebuilds/fixes using a VCS so that they could be shared and |
| 23 |
> easily pulled and applied to the main tree. It takes too long to |
| 24 |
> browse bugzilla, find bugs, find ebuilds and patches, download them, |
| 25 |
> copy to an overlay, fix digests, emerge, etc. and most users will |
| 26 |
> figure it's not worth the hassle. |
| 27 |
Yes, i agree, writting and maintaining ebuilds is a hard and |
| 28 |
*time-consuming* task. |
| 29 |
So if an user can't even take the time to fix a digest, why we should |
| 30 |
support him |
| 31 |
officially?. |
| 32 |
|
| 33 |
-- |
| 34 |
gentoo-dev@g.o mailing list |
Archives