1 |
On 14.6.2010 5.59, Jeroen Roovers wrote: |
2 |
> On Mon, 14 Jun 2010 00:29:19 +0200 |
3 |
> Pacho Ramos <pacho@g.o> wrote: |
4 |
> |
5 |
>> El dom, 13-06-2010 a las 14:43 +0200, Pacho Ramos escribió: |
6 |
>>> El dom, 13-06-2010 a las 14:16 +0300, Petteri Räty escribió: |
7 |
>>>> On 06/11/2010 12:27 PM, Pacho Ramos wrote: |
8 |
>>>> |
9 |
>>>>> |
10 |
>>>>> From my point of view, I would prefer to: |
11 |
>>>>> 1. Mask "caps" for net-wireless/bluez on affected arches, |
12 |
>>>>> letting us to keep bluez keyworded. |
13 |
>>>>> 2. Open two bug reports as done with current policy: one for |
14 |
>>>>> keywording libcap-ng and other to check bluez works ok with it |
15 |
>>>>> asking arch team to unmask that USE flag if possible. |
16 |
>>>>> |
17 |
>>>> |
18 |
>>>> There's nothing preventing you from already doing this. |
19 |
>>>> package.use.mask is something package maintainers themselves |
20 |
>>>> should be looking after for their packages. |
21 |
>>>> |
22 |
>>>> Regards, |
23 |
>>>> Petteri |
24 |
>>>> |
25 |
>>> |
26 |
>>> |
27 |
>>> OK, thanks a lot :-D |
28 |
>> |
29 |
>> The problem is that hppa team seems to not allow others than they to |
30 |
>> edit their package.use.mask :-/, is there any special reason for it? |
31 |
> |
32 |
> What is the problem? The files in place ask you to file a bug report |
33 |
> instead of fiddling with the files yourselves. I put that in place |
34 |
> because I got (fucking) tired of seeing the after effects of people |
35 |
> fiddling with the arch profile files without 1) consideration, 2) |
36 |
> informing the involved arch team. What do you expect? |
37 |
|
38 |
If there's a problem with how developers do stuff shouldn't we rather |
39 |
educate them and make sure new developers are trained so there will not |
40 |
be many problems? Aren't arch teams overloaded for work already? |
41 |
package.use.mask is local to a single package so usually there's not a |
42 |
big need for arch teams to be aware of the entries (unless of course |
43 |
it's some central package but hopefully their maintainers have due |
44 |
diligence). |
45 |
|
46 |
Regards, |
47 |
Petteri |