public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion related with dropping keywords policy
Date: Mon, 14 Jun 2010 10:08:58 +0200	[thread overview]
Message-ID: <1276502938.6652.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20100614045910.7a513829@epia.jer-c2.orkz.net>

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

El lun, 14-06-2010 a las 04:59 +0200, Jeroen Roovers escribió:
> What is the problem? The files in place ask you to file a bug report
> instead of fiddling with the files yourselves. I put that in place
> because I got (fucking) tired of seeing the after effects of people
> fiddling with the arch profile files without 1) consideration, 2)
> informing the involved arch team. What do you expect? File a bloody bug
> report detailing the (commit) problem you are facing and you will
> probably see 1) response and 2) cooperation. If you fuck around with
> the arch profile files without doing any of that, you will face 1) a
> lack of willingness to cooperate and 2) evil wrath.
> 
> 
> Regards,
>      jer

The problem is that, at least regarding gnome related bugs, there are a
lot of keywords dropped for your arch that could be prevented
use.masking an USE, like, for example, dev-util/anjuta-2.28*, that is
causing us to preserve and old (and broken) 2.24 release only for hppa.

My intention is only to try to help you and improve the situation, I
also have opened bug reports for every change have committed to, for
example, powerpc profiles (you will see that I edited your profile
yesterday, but it was because I totally missed the note preventing us to
do that, this is why I didn't committed any more changes and sent reply
above; it wasn't premeditated)

Would you allow me to edit hppa package.use.mask *if I open
corresponding bug report* ?

Thanks :-)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-06-14  8:09 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
2010-06-14  2:59       ` Jeroen Roovers
2010-06-14  8:08         ` Pacho Ramos [this message]
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=1276502938.6652.4.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