Gentoo Archives: gentoo-dev

From: Paul de Vrieze <pauldv@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC: GLEP 49 - Package manager requirements
Date: Sun, 21 May 2006 10:45:38
Message-Id: 200605211238.56080.pauldv@gentoo.org
In Reply to: Re: [gentoo-dev] RFC: GLEP 49 - Package manager requirements by Brian Harring
1 On Sunday 21 May 2006 05:44, Brian Harring wrote:
2 > So... where's the standard? :)
3 > Right, no doc yet that's official, thus at this juncture, what's
4 > there now (portage) is the effective standard.
5 >
6 > Said in the last thread, chunking out a formal EAPI=0 definition from
7 > the tree/portage implementation, tiz a good thing. But until that's
8 > done (and folks agree it's the standard), portage (primary manager)
9 > rules, thus doc it out (as I've suggested to ciaran for the
10 > slot value and use/slot dep restrictions he's added) if you're after
11 > changing the existing definition.
12 >
13 > Not saying I like it, but it's the reality of current situation- the
14 > intention of the glep is to prevent lock in, and to keep the tree
15 > unified in terms of support (avoid fracturing of the env the tree has
16 > been written against), either a doc standard is created for EAPI=0, or
17 > portage defines the standard (since it's primary).
18
19 I have just committed my current revision. It includes some things about this.
20 That the standard is not only the implementation, but also guidelines etc.
21 This section is intended to convey that the maintainers of the primary
22 package manager can define (keeping the gentoo processes into account) new
23 extensions to the standard, or a new EAPI=1 version.
24
25 > > The process should go like this:
26 > >
27 > > 1. Standars are set (by the council or whatever).
28 > > 2. They are implemented in the official package manager.
29 > > 3. Other package managers follow suit.
30 >
31 > Council really shouldn't be involved sans big changes imo, and big
32 > changes imo should require gleps (both from an archive standpoint, and
33 > from fitting the council in via existing process of gleps).
34
35 I agree with this.
36 >
37 > One concern out of all of this is ensuring that their isn't
38 > ping/ponging back and forth as to which manager is 'official'; arms
39 > race in terms of features supported by each manager is a good thing
40 > imo, but need to keep that from causing chaos for devs in terms of
41 > changing standards.
42
43 The point indeed.
44
45 Paul
46
47 --
48 Paul de Vrieze
49 Gentoo Developer
50 Mail: pauldv@g.o
51 Homepage: http://www.devrieze.net

Replies

Subject Author
[gentoo-dev] Re: RFC: GLEP 49 - Package manager requirements Duncan <1i5t5.duncan@×××.net>