From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: hppa@gentoo.org
Subject: Re: [gentoo-dev] Suggestion related with dropping keywords policy
Date: Mon, 14 Jun 2010 00:29:19 +0200 [thread overview]
Message-ID: <1276468159.1413.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1276433026.868.0.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
El dom, 13-06-2010 a las 14:43 +0200, Pacho Ramos escribió:
> El dom, 13-06-2010 a las 14:16 +0300, Petteri Räty escribió:
> > On 06/11/2010 12:27 PM, Pacho Ramos wrote:
> >
> > >
> > > 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.
> > >
> >
> > There's nothing preventing you from already doing this. package.use.mask
> > is something package maintainers themselves should be looking after for
> > their packages.
> >
> > Regards,
> > Petteri
> >
>
>
> OK, thanks a lot :-D
The problem is that hppa team seems to not allow others than they to
edit their package.use.mask :-/, is there any special reason for it?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-13 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 9:27 [gentoo-dev] Suggestion related with dropping keywords policy Pacho Ramos
2010-06-11 9:39 ` 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 [this message]
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=1276468159.1413.2.camel@localhost.localdomain \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=hppa@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