public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Parpart <trapni@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] apache and ~arch
Date: Mon, 14 Mar 2005 16:39:02 +0100	[thread overview]
Message-ID: <200503141639.04696.trapni@gentoo.org> (raw)
In-Reply-To: <20050314144341.3017e91b@snowdrop>

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

On Monday 14 March 2005 3:43 pm, Ciaran McCreesh wrote:
> On Sun, 13 Mar 2005 11:24:41 -0600 Grant Goodyear <g2boojum@gentoo.org>
> wrote:
> | However, I don't believe that ~arch should be used for ebuilds
> | that one _knows_ have broken functionality.  For such cases we
> | have package.mask.
>
> Indeed. It's in the developer docs and it's in the quiz. And yet...
>
> http://planet.gentoo.org/developers/hollow/2005/03/14/apache_dithering

He still does great work. So, please don't stick on words written down in hot 
times.

> > I can understand that breaking the system isn't a very good idea and
> > people will complain, but this does not count for the testing branch.
>
> *sigh* Er, no. If you *know* it's broken, don't stick it in ~arch. If
> it has no known issues, but hasn't been widely tested, then ~arch is
> fine, but not if it's completely h0rked.

FYI, mod_php wasn't "completely borked". It's just not been unmasked at the 
same time as the others went out of the hardmask state.

> For how long have these people been developers and who were their
> mentors? I'm starting to think that this wasn't a simple mistake --
> rather, that it's a complete misunderstanding of what the different
> KEYWORDS levels mean...

I - in my case - have learned my lessons from this - who cares.

Regards,
Christian Parpart.

-- 
Netiquette: http://www.ietf.org/rfc/rfc1855.txt
 16:27:26 up 136 days,  8:57,  1 user,  load average: 0.12, 0.21, 0.24

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-14 15:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-13 17:24 [gentoo-dev] apache and ~arch Grant Goodyear
2005-03-14  0:17 ` kang
2005-03-14  9:23 ` Michael Stewart
2005-03-14 15:56   ` Grant Goodyear
2005-03-14 14:43 ` Ciaran McCreesh
2005-03-14 15:39   ` Christian Parpart [this message]
2005-03-14 16:57   ` Jochen Maes
2005-03-14 17:17     ` Marius Mauch
2005-03-15  9:08       ` Sven Vermeulen
2005-03-15 15:20         ` Ciaran McCreesh
2005-03-14 17:20     ` Ciaran McCreesh
2005-03-22 13:50 ` Paul de Vrieze
2005-03-22 14:32   ` Aaron Walker

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=200503141639.04696.trapni@gentoo.org \
    --to=trapni@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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