Stefan Schweizer wrote:
comments?
just find a scriptable system to manage server side mass keywording...
as in
$EDITOR tokeywordfile
(same syntax as package.keywords)
repoman tokeywords tokeywordfile
(repoman first checks it is applicable locally and then push it over the
server while
To my fellow arguing Gentoo developers,
due to the recent conflict concerning keywording I want to propose to
separate keywording completely from ebuilds. The keywords would reside
in a special file in profiles/, maybe even in more than one file to
allow more granular permissions. For example
Monday, 19. February 2007, Stefan Schweizer Ви написали:
To my fellow arguing Gentoo developers,
due to the recent conflict concerning keywording I want to propose to
separate keywording completely from ebuilds. The keywords would reside
in a special file in profiles/, maybe even in more than
It was discussed at the last council meeting... Proposed by jokey.
On Mon, Feb 19, 2007 at 10:54:55AM +0100, Stefan Schweizer wrote:
To my fellow arguing Gentoo developers,
due to the recent conflict concerning keywording I want to propose to
separate keywording completely from ebuilds. The
On Mon, Feb 19, 2007 at 10:54:55AM +0100, Stefan Schweizer wrote:
To my fellow arguing Gentoo developers,
due to the recent conflict concerning keywording I want to propose to
separate keywording completely from ebuilds. The keywords would reside
in a special file in profiles/, maybe even in
On Monday 19 February 2007, Bryan Østergaard wrote:
That's lame for several different reasons that I'm going to outline
below and frankly anybody blowing steam about ~arch keywording the
latest version (which ended up as being the goal yesterday) is being
extremely silly.
i dont add my voice
Dňa Mon, 19 Feb 2007 12:34:19 +0100
Bryan Østergaard [EMAIL PROTECTED] napísal:
Anyway, here's several reasons why it's lame - I'm sure there's even
more good reasons but these should suffer:
Another reason would be that it would cripple (even more) the benefit
of having all the relevant info
