From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.3/8.13.3) with ESMTP id j2AFuab1024458 for ; Thu, 10 Mar 2005 15:56:37 GMT Received: from smtp.nuvox.net ([64.89.70.9] helo=smtp05.gnvlscdb.sys.nuvox.net) by smtp.gentoo.org with esmtp (Exim 4.43) id 1D9Q1b-0008Pm-Tz for gentoo-dev@robin.gentoo.org; Thu, 10 Mar 2005 15:56:36 +0000 Received: from cgianelloni.nuvox.net (216.215.202.4.nw.nuvox.net [216.215.202.4]) by smtp05.gnvlscdb.sys.nuvox.net (8.12.11/8.12.11) with SMTP id j2AFuiqO017983 for ; Thu, 10 Mar 2005 10:56:44 -0500 Received: by cgianelloni.nuvox.net (sSMTP sendmail emulation); Thu, 10 Mar 2005 11:00:52 -0500 Subject: Re: [gentoo-dev] Please follow keywording policy From: Chris Gianelloni To: gentoo-dev@robin.gentoo.org In-Reply-To: <4230071B.7040401@gentoo.org> References: <20050308185536.58ecbe3c@enterprise.weeve.org> <422EA7E2.4040206@gentoo.org> <422EFCA6.2010607@gentoo.org> <422F0D2E.1040301@gentoo.org> <20050309162258.624316be@snowdrop> <422F3482.8020607@gentoo.org> <20050309183846.426af19a@snowdrop> <422F46F3.4030208@gentoo.org> <422F7F4B.4090406@gentoo.org> <20050310043425.GF10754@dst.grantgoodyear.org> <4230071B.7040401@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-cxoQv5BMO8iwbBeW6WyS" Organization: Gentoo Linux Date: Thu, 10 Mar 2005 11:00:51 -0500 Message-Id: <1110470451.21812.21.camel@cgianelloni.nuvox.net> Precedence: bulk List-Post: , , List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-To: gentoo-dev@gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 X-Archives-Salt: b77c5430-d482-44ca-88f1-191a64a8ce89 X-Archives-Hash: ab0d4a37198a9c7307b7d30be072ef80 --=-cxoQv5BMO8iwbBeW6WyS Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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=20 > package because this is not always possible. Usually, I add the new=20 > ebuild with ~x86 and let testing to the user who request that. It may=20 > not be the orthodox way, but the risk of breaking something else in the=20 > 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 >=3Dfoo-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=20 > take silence as a sign that everything works. I am sure I'm not the only=20 > 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=20 > 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. --=20 Chris Gianelloni Release Engineering - Strategic Lead/QA Manager Games - Developer Gentoo Linux --=-cxoQv5BMO8iwbBeW6WyS Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQBCMG8zkT4lNIS36YERAh8lAKCa0WAIMSSH+EzspRVS3CmcZn0vWwCgwgt2 FkMBbZJtC4RBxbr+jbxditk= =CFWs -----END PGP SIGNATURE----- --=-cxoQv5BMO8iwbBeW6WyS-- -- gentoo-dev@gentoo.org mailing list