public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Thu, 10 Mar 2005 11:00:51 -0500	[thread overview]
Message-ID: <1110470451.21812.21.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <4230071B.7040401@gentoo.org>

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

On Thu, 2005-03-10 at 10:36 +0200, Alin Nastac wrote:
> Not every time when I receive a new ebuild submittion, I also test that 
> package because this is not always possible. Usually, I add the new 
> ebuild with ~x86 and let testing to the user who request that. It may 
> not be the orthodox way, but the risk of breaking something else in the 
> process is 0 (a new ebuild means no other ebuilds depends on it).

Add it as ~arch and p.mask it, or get more people to test it *while it
is still in bugzilla* until you are pretty sure that it works, *then*
add it.

If an ebuild has a DEPEND on >=foo-1.0 and you add foo-1.2, then it
*will* be pulled in as a dependency, so you can't possibly say that
nothing depends on it and be serious.

> Users don't usually come to me and say "that ebuild works for me". I 
> take silence as a sign that everything works. I am sure I'm not the only 
> one doing that.

No.  Everyone else is making sure the ebuild works before adding it.
The truth is that you've just been lucky, so far.

> I ask arches to mark a new ebuild as stable because a know bug have been 
> solved or because the old stable version breaks something else.

Great.  Don't start a hissy fit on -dev when they don't mark it stable
because they can't test it.  Especially when you haven't made a good
effort to contact them to resolve the problem.  Airing your dirty
laundry out in public just makes you look white trash... ;]  This isn't
Jerry Springer.  We don't need to know who your baby's daddy is.  A
simple email to the mips team could have kept all of this from even
being an issue.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-03-10 15:56 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  1:55 [gentoo-dev] Please follow keywording policy Jason Wever
2005-03-09  2:00 ` Hasan Khalil
2005-03-09  7:38 ` Alin Nastac
2005-03-09 13:39   ` Stephen P. Becker
2005-03-09 14:50     ` Alin Nastac
2005-03-09 16:22       ` Ciaran McCreesh
2005-03-09 17:38         ` Alin Nastac
2005-03-09 18:38           ` Ciaran McCreesh
2005-03-09 18:56             ` Alin Nastac
2005-03-09 19:10               ` Stefan Schweizer
2005-03-09 19:10                 ` Stefan Schweizer
2005-03-09 21:30                 ` Luis F. Araujo
2005-03-09 22:57                 ` Alin Nastac
2005-03-09 23:27                   ` Stephen P. Becker
2005-03-10  0:50                     ` Donnie Berkholz
2005-03-10  0:18                       ` Daniel Goller
2005-03-09 23:36                   ` Jason Wever
2005-03-09 23:42                   ` Aron Griffis
2005-03-10  7:54                     ` Alin Nastac
2005-03-10  8:27                       ` Ciaran McCreesh
2005-03-10 15:54                         ` Chris Gianelloni
2005-03-10 15:52                       ` Chris Gianelloni
2005-03-10  4:34                   ` Grant Goodyear
2005-03-10  8:36                     ` Alin Nastac
2005-03-10 13:14                       ` Ciaran McCreesh
2005-03-10 16:00                       ` Chris Gianelloni [this message]
2005-03-10 19:00                         ` Alin Nastac
2005-03-10 19:33                           ` Chris Gianelloni
2005-03-10 21:25                             ` John Myers
2005-03-10 15:38                   ` Chris Gianelloni
2005-03-09 19:18               ` Patrick Lauer
2005-03-09 19:43                 ` Stefan Schweizer
2005-03-09 19:56                   ` Patrick Lauer
2005-03-10  0:55               ` Jon Portnoy
2005-03-10  8:07                 ` Alin Nastac
2005-03-09 19:20             ` Chris Gianelloni
2005-03-09 16:37       ` Stephen P. Becker
2005-03-09 16:43   ` Chris Gianelloni
2005-03-09 17:40     ` Alin Nastac

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=1110470451.21812.21.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@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