public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] QA Overlay Layout support.
Date: Mon, 02 Mar 2009 17:05:00 +0100	[thread overview]
Message-ID: <49AC03AC.9090400@gentoo.org> (raw)
In-Reply-To: <49AB7A52.3060401@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2198 bytes --]

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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 315 bytes --]

      parent reply	other threads:[~2009-03-02 16:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-24 22:59 [gentoo-dev] QA Overlay Layout support Alistair Bush
2009-01-26  4:59 ` Alistair Bush
2009-03-01 23:01 ` Jorge Manuel B. S. Vicetto
2009-03-02  3:11 ` Donnie Berkholz
2009-03-02  6:18   ` Alistair Bush
2009-03-02  6:57     ` Donnie Berkholz
2009-03-02  7:57       ` Alistair Bush
2009-03-02  9:29         ` Jorge Manuel B. S. Vicetto
2009-03-02 20:01           ` Wulf C. Krueger
2009-03-05  1:52             ` Jorge Manuel B. S. Vicetto
2009-03-06  9:55               ` Caleb Cushing
2009-03-03  7:19         ` Caleb Cushing
2009-03-03  7:43           ` [gentoo-dev] " Duncan
2009-03-03 10:56           ` [gentoo-dev] " Marijn Schouten (hkBst)
2009-03-03 12:42           ` Petteri Räty
2009-03-02 16:05     ` Thomas Sachau [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49AC03AC.9090400@gentoo.org \
    --to=tommy@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox