Alistair Bush schrieb:
> Asking non-dev contributors to handle package.mask's would be a "less
> than ideal". Resulting in "interesting breakages".  Currently by adding
> java-experimental ( which might I add isn't available thru layman ) you
> are accepting that risk.
> 
> At least java and kde have need of this,  and I could imagine sunrise
> could also use this ( either now or in the future ).

> Contributors sometimes have difficulty following standards (hell even
> dev's do).  I have little confidence that would also be able to actually
> add packages to package.mask without breaking anything else.
> As an example we had a contributor break the manifests of a dozen or so
> packages because he updated the Copyright header then couldn't get the
> ebuild to manifest.  I can imagine someone committing dev-java/ant-core
> to the file.  That and there are 325 ebuilds [1] in java-experimental.
> Masking even 1/2 of them separately would be a complete nightmare.
>
> I also note that sunrise doesn't seem to do this either.

Just to explain it a bit, also it should be documented in the docs (if not, 
patches are welcome):

Sunrise has the sunrise/ tree, where you can only read and write with a 
password (=reading our
HowtoCommit and having an ebuild reviewed). All initial commits go into this 
part, but since this is
only internal, the commits cannot harm any user.
For the second step, we have the reviewed/ tree, which is public and used by 
layman. The sunrise/
tree is reviewed by the sunrise devs and after all commits where reviewed, the 
changes in sunrise/
where merged into reviewed/.
Since the packages are still experimental (we only do a basic review on the 
ebuilds), we only allow
and accept ~ARCH for normal ebuilds and no KEYWORDS for live ebuilds. This way, 
a stable user has to
explicitly keyword a package, before he can install it from sunrise.

Since this is a different concept then those of kde and java (where users can 
add code without some
basic qa check and review), i dont see a need for your request on sunrise side, 
but if i missed
something, feel free to enlighten me.


-- 
Thomas Sachau

Gentoo Linux Developer

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to