From: Jason Wever <weeve@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Wed, 9 Mar 2005 16:36:32 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.62.0503091629340.24050@stargazer.weeve.org> (raw)
In-Reply-To: <422F7F4B.4090406@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 10 Mar 2005, Alin Nastac wrote:
> I'm only annoyed by the bad attitude of some devs who will get involved only
> what suits them, forgetting that if they would not help, no one will. Btw,
> what is the sense of ~arch if not "testing"? No gentooer expects from a ~arch
> ebuild to be stable, so the sky would not fall if you made a mistake and
> release it under this keyword. When I hear "I cannot mark foo library as
> ~arch because I don't know how to test it" smells like excuse to me.
When a package is marked ~arch, it's also supposed to work (or have worked
in a previous version).
Also it may help to look at things from an arch maintainers points of
view. We are responsible for essentially maintaining almost every package
in the tree for our architecture. When we ask for testing criteria with
regards to a request for keywording, it's because it makes both of our
lives easier and helps to improve QA as we arch maintainers don't know a
lot about your application and don't have the time to get to know it like
you do. This is especially helpful when dealing with libraries.
Cheers,
- --
Jason Wever
Gentoo/Sparc Co-Team Lead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFCL4iCdKvgdVioq28RAhqxAKC2MDFXkkHaX97d2FyX22H4V7Q0ZACgg9Fm
SCaOh/OJ0fjnnDZVZRutG9A=
=snEB
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-09 23:36 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 [this message]
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
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=Pine.LNX.4.62.0503091629340.24050@stargazer.weeve.org \
--to=weeve@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