Daniel, answering you in this mail... Yes, probably sometimes we have to
discuss basic things in this mailing list but since developers do this
basic errors we have to. Technical problems in our portage tree are
perfectly valid for this mailing list.
В Пнд, 05/01/2009 в 13:55 +0530, Nirbheek
В Вск, 04/01/2009 в 18:57 +0100, Robert Buchholz пишет:
On Sunday 04 January 2009, Mike Auty wrote:
Jeroen Roovers wrote:
The order (first maintainer as assignee or first maintainer/herd
as assignee) is open to discussion and I think this is the proper
forum to have that discussion.
On Sun, Jan 04, 2009 at 06:12:17PM +, Mike Auty wrote:
a) herds.xml per-herd priority flag (herd gets assigned)
b) metadata.xml priority element (can be opt-in or opt-out)
c) order of elements in metadata.xml
I'm personally not keen on the order of elements, since adding meaning
to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin H. Johnson wrote:
Neither set of rules is ideal. Ordering makes a lot of sense when you
just read it. Consider metadata with multiple maintainers and multiple
herds. Either you have to start assigning explicitly (requires editing
On Wed, 31 Dec 2008 01:12:23 +0100
Fabio Rossi ross...@inwind.it wrote:
I'm proposing to reorganize the files related to Gentoo
inside /var/lib. Currently we have this situation (at least on my
system):
/var/lib/eselect
/var/lib/gentoo/enews
/var/lib/herdstat/
/var/lib/module-rebuild
On Mon, 15 Dec 2008 23:47:47 + (UTC)
Duncan 1i5t5.dun...@cox.net wrote:
While I'm at it, is there anything useful to display metadata.xml?
In particular, the long descriptions and use flags can be useful.
With use.desc and especially the local version thereof going
deprecated, and with
Am Sonntag, den 04.01.2009, 18:06 +0100 schrieb Jeroen Roovers:
On Sun, 04 Jan 2009 17:02:21 +
Mike Auty ike...@gentoo.org wrote:
According to [1], When the file lists multiple entries, then you
assign the bug to the first maintainer, and CC the other
maintainer(s) and herd(s). So
