| 1 |
On Sun, 16 Feb 2014 14:48:57 +0100 |
| 2 |
Jeroen Roovers <jer@g.o> wrote: |
| 3 |
|
| 4 |
> On Sun, 16 Feb 2014 08:23:27 +0100 |
| 5 |
> Tom Wijsman <TomWij@g.o> wrote: |
| 6 |
> |
| 7 |
> > > > While it was not explained here, the idea can also move the |
| 8 |
> > > > actual maintenance of the ebuild to the arch team; such that it |
| 9 |
> > > > becomes the arch team's responsibility to deal with it, or |
| 10 |
> > > > rather don't deal with it |
| 11 |
> > > |
| 12 |
> > > How would that ever work? |
| 13 |
> > |
| 14 |
> > The responsibility is moved away from the maintainer; and thus also |
| 15 |
> > its bugs, as well as the need to rely on a newer version to become |
| 16 |
> > stable. |
| 17 |
> |
| 18 |
> The (slightly rhetorical) question was how an understaffed team could |
| 19 |
> be realistically expected to start maintaining ebuilds. Your entire |
| 20 |
> reply missed that point. |
| 21 |
> |
| 22 |
> The answer to the question is that you can't. |
| 23 |
|
| 24 |
The deepest quote contains "or rather don't deal with it". |
| 25 |
|
| 26 |
-- |
| 27 |
With kind regards, |
| 28 |
|
| 29 |
Tom Wijsman (TomWij) |
| 30 |
Gentoo Developer |
| 31 |
|
| 32 |
E-mail address : TomWij@g.o |
| 33 |
GPG Public Key : 6D34E57D |
| 34 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives