1 |
On Mon, Aug 14, 2017 at 2:42 PM, Peter Stuge <peter@×××××.se> wrote: |
2 |
> |
3 |
> I am sure |
4 |
> that portage developers gnash their teeth at blockers stemming from |
5 |
> PMS, but I wholeheartedly believe that Gentoo, PMS and Portage are |
6 |
> all better off for it. |
7 |
> |
8 |
|
9 |
Honestly, I've yet to see any portage developers complaining about PMS here. |
10 |
|
11 |
In general the main hoops to jump through if you want something in PMS are: |
12 |
|
13 |
1. A well-thought-out design. (May involve list bikeshedding/etc, |
14 |
with input from the portage team and other interested parties being |
15 |
key.) |
16 |
2. A portage implementation. (Which is an issue if you want |
17 |
something in portage no matter what.) |
18 |
3. Council approval. (Which tends to happen if you have #1-2 and |
19 |
aren't just ignoring list feedback.) |
20 |
|
21 |
It is pretty common for people to do them in the order 1-3-2 with 3 |
22 |
being a provisional approval so that the portage developers don't spin |
23 |
their wheels. |
24 |
|
25 |
Usually when #1 ends up being the hangup there tend to be serious |
26 |
concerns about how the concept will work in reality. If it will make |
27 |
ebuilds harder to maintain or their behavior less predictable then an |
28 |
implementation alone isn't enough. Either that or there are concerns |
29 |
that the design doesn't fully address the need, which often happens |
30 |
when we add a new dependency type. |
31 |
|
32 |
IMO the process isn't really broken, and I doubt that changing the |
33 |
name would change anything. We don't wait for other package managers |
34 |
to support a new PMS version before using it in the tree. We do value |
35 |
the input of anybody with expertise in this area, though the Council |
36 |
holds the final say. PMS has a huge impact on our QA and I think |
37 |
we're generally better off for the time spent on it. |
38 |
|
39 |
If somebody actually does have a PMS proposal that has been stalled it |
40 |
wouldn't hurt to share it, or if the portage team feels otherwise. |
41 |
|
42 |
-- |
43 |
Rich |