W dniu 03.02.2011 08:39, Torsten Veller pisze:
> * Theo Chatzimichos <[email protected]>:
>> For the record, Kacper told me today that every developer is allowed to 
>> touch 
>> ppc/ppc64 profiles. Archies that don't want others to touch their profiles 
>> should mention it in the devmanual. I was not aware of that, I thought that 
>> !arch member is not allowed to touch arch-specific profiles.
Just to be clear I was talking about package.mask file. Kitten-forbid
you tweak e.g. make.defaults.

Honestly, I don't see the reasons why dev should be forbid to *add* pkgs
to package.mask file for other profiles that inherit base.
*Removing* is quite different, but again common sense advise you
shouldn't lift it until reason for masking is gone. That you cannot
verify if you're not an arch member.

> The situation is complicated:
<snip>
> - Some arch teams don't want other devs to touch "their" profiles:
>   "DON'T TOUCH THIS FILE. Instead, file a bug and assign it to..."
>   But this arch is neiter mentioned in the handbook nor in the manual:
>   
> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=5#doc_chap4
>   http://devmanual.gentoo.org/archs/index.html

Clearly if something is written in bold and at the very top of the file
you should respect. I'm sure there are reasons for it and I've never
seen that particular arch being unresponsive.

> - The devhandbook[2] is also kind of unmaintained.
>   Devmanual and -handbook are waiting for a merge AFAIR.
> 
> - And there is already a stalled bug[3] about "Developer Handbook should
>   document how/when to touch arch profiles' files"
> 
> Summary: You do it wrong either way.

The problem actually boils down to asking... Arch team members are out
there on irc, have mail aliases, etc. This very thread was started due
to lack of communication. It could have looked like that:

KDE: I would like to unmask KDE-4.6.0 in base, but that requires mask in
ppc64/package.mask. Can I do it?
PPC64: Sure, go ahead.

and it would have taken approx. 30s

Cheers,
Kacper

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to