Bryan Østergaard wrote:
A. ~arch keywords are supposed to be carried over to new versions unless
we're talking about big rewrites or similar (so old versions doesn't
have to linger around in portage tree at all).
right, we all agree :)
B. If we're complaining about MIPS team not being able to
Alexander Færøy schrieb:
It was discussed at the last council meeting... Proposed by jokey.
Thanks. Sorry I did not know about it because there was no summary for
the last council meeting. From the log that I read now I cannot clearly
define an outcome.
I would appreciate to see summaries
On Mon, Feb 19, 2007 at 03:16:06PM +0100, Stefan Schweizer wrote:
Alexander Færøy schrieb:
It was discussed at the last council meeting... Proposed by jokey.
Thanks. Sorry I did not know about it because there was no summary for
the last council meeting. From the log that I read now I
On Mon, Feb 19, 2007 at 03:13:00PM +0100, Stefan Schweizer wrote:
Bryan Østergaard wrote:
A. ~arch keywords are supposed to be carried over to new versions unless
we're talking about big rewrites or similar (so old versions doesn't
have to linger around in portage tree at all).
right, we all
George Shapovalov schrieb:
a) move all the keywording into profiles (that is remove all KEYWORDS fields
from all the ebuild) and disallow package maintainers and other devs (other
than arch teams) to touch keywords
or
b) leave ebuilds with simple ~arch/arch/-arch (literally) keywords and
On Mon, 2007-02-19 at 15:37 +0100, Stefan Schweizer wrote:
moving keywording only in the arch teams responsibility is the way to go
imo because I hate having keywording bugs assigned to my herd where I
can do nothing about it.
Uhh... so why *don't* you assign these to the arch teams?
Here's
