From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Suggestion related with dropping keywords policy
Date: Fri, 11 Jun 2010 11:27:22 +0200 [thread overview]
Message-ID: <1276248442.17113.16.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
Hello
Let my explain the problem and my suggestion to handle it better (at
least from my point of view) with an example:
Sometime ago I bumped bluez version from 4.39-r2 to 4.60, with that
bump, a new and *optional* RDEPEND on sys-libs/libcap-ng was added.
Since libcap-ng was not keyworded in all arches but x86 and amd64, I had
to drop keywords for bluez and open
http://bugs.gentoo.org/show_bug.cgi?id=303527 for handling it.
From my point of view, I would prefer to:
1. Mask "caps" for net-wireless/bluez on affected arches, letting us to
keep bluez keyworded.
2. Open two bug reports as done with current policy: one for keywording
libcap-ng and other to check bluez works ok with it asking arch team to
unmask that USE flag if possible.
This way to go would have the advantage of letting people running bluez
on affected arches to still get the latest bluez version instead of
still having to run a pretty old (and buggy) one.
Thanks for considering it
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-06-11 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 9:27 Pacho Ramos [this message]
2010-06-11 9:39 ` [gentoo-dev] Suggestion related with dropping keywords policy Thilo Bangert
2010-06-11 11:39 ` Joseph Jezak
2010-06-17 4:07 ` Jeroen Roovers
2010-06-17 12:04 ` Pacho Ramos
2010-06-17 17:41 ` Jeroen Roovers
2010-06-13 11:16 ` Petteri Räty
2010-06-13 12:43 ` Pacho Ramos
2010-06-13 22:29 ` Pacho Ramos
2010-06-14 2:59 ` Jeroen Roovers
2010-06-14 8:08 ` Pacho Ramos
2010-06-14 9:30 ` Jeroen Roovers
2010-06-14 9:44 ` Pacho Ramos
2010-06-14 8:21 ` Petteri Räty
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=1276248442.17113.16.camel@localhost.localdomain \
--to=pacho@gentoo.org \
--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