1 |
Steve Long <slong@××××××××××××××××××.uk> posted |
2 |
ekol7b$q8i$1@×××××××××.org, excerpted below, on Fri, 01 Dec 2006 07:23:09 |
3 |
+0000: |
4 |
|
5 |
> Excellent; pkgcore really sounds great- is there any possibility that it'll |
6 |
> become the new portage? |
7 |
|
8 |
Possibility, yes. It's not certain, as there are multiple contenders |
9 |
(paludis is the other), and it will be some time, in any case. |
10 |
|
11 |
The current problem is that there's no standard definition for what |
12 |
constitutes an acceptable ebuild, beyond the basic gentoo dev guidelines. |
13 |
The de facto definition is whatever works with versions of portage |
14 |
currently in the tree (or just barely removed), but that presents many |
15 |
difficulties, including both slow upgrades since backward compatibility |
16 |
must be maintained for longer even when the former functionality is |
17 |
considered b0rken, and questions of what's broken, the package manager or |
18 |
the ebuild, when something fails to work as expected. |
19 |
|
20 |
Thus, all three package managers, the current portage solution, and paludis |
21 |
and pkgcore as well, are currently under slower development than they might |
22 |
otherwise be, while interested parties attempt to hash out a working |
23 |
standard definition of what actually constitutes a proper ebuild, and |
24 |
what helper functions said ebuild can in fact depend upon the package |
25 |
manager to make available. Once that's decided and approved, the playing |
26 |
field upon which the merits of the next generation package managers can be |
27 |
judged will be much fairer for all. Of course, with that defined, portage |
28 |
itself will be freer to progress at speed as well, and it may be that it |
29 |
will remain the default "approved" solution for quite some time. |
30 |
|
31 |
-- |
32 |
Duncan - List replies preferred. No HTML msgs. |
33 |
"Every nonfree program has a lord, a master -- |
34 |
and if you use the program, he is your master." Richard Stallman |
35 |
|
36 |
-- |
37 |
gentoo-dev@g.o mailing list |