From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: new developers' keyword requests
Date: Sat, 21 May 2016 07:08:11 +0000 (UTC) [thread overview]
Message-ID: <pan$7be88$5338fa85$44d7261b$945a511@cox.net> (raw)
In-Reply-To: CAEdQ38GVspO5xTaf9yDAHHKFTj3QYXT=kG-wBqi-k+YiAAE8_w@mail.gmail.com
Matt Turner posted on Fri, 20 May 2016 21:47:56 -0700 as excerpted:
> He's saying people add new packages and then speculatively add keywords
> for a bunch of architectures that they haven't tested. This causes
> unnecessary packages to be keyworded on archs that don't want them and
> can hardly afford the extra load.
I can even visualize the argument in support, too.
"Well, the package is known to work on that arch on Fedora..."
That may be, but has the package been actually tested to work on that
arch within the gentoo context, and is it likely to be practical for the
minor arch to continue to support? It's not a question of whether it
worked on fedora or not. It's a question of whether it has been tested
on gentoo or not, and whether that arch's users on gentoo find it useful
enough to be worth the trouble to maintain over time and other software
changes on that arch.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-05-21 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 14:51 [gentoo-dev] new developers' keyword requests Jeroen Roovers
2016-05-19 15:00 ` Mike Gilbert
2016-05-20 1:36 ` Daniel Campbell
2016-05-20 12:38 ` Kristian Fiskerstrand
2016-05-20 13:11 ` Kristian Fiskerstrand
2016-05-20 13:34 ` M. J. Everitt
2016-05-20 13:20 ` Daniel Campbell
2016-05-20 14:00 ` Jeroen Roovers
2016-05-21 2:09 ` Ian Delaney
2016-05-21 2:35 ` Sam Jorna
2016-05-21 4:47 ` Matt Turner
2016-05-21 6:41 ` Daniel Campbell
2016-05-21 7:08 ` Duncan [this message]
2016-05-21 9:01 ` Jeroen Roovers
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='pan$7be88$5338fa85$44d7261b$945a511@cox.net' \
--to=1i5t5.duncan@cox.net \
--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