| 1 |
Ciaran McCreesh wrote: |
| 2 |
> I've got the EAPI 3 branch for PMS more or less ready: |
| 3 |
> |
| 4 |
> http://github.com/ciaranm/pms/tree/eapi-3 |
| 5 |
> |
| 6 |
> The provisional included feature list is everything that was ready |
| 7 |
> before the deadline. |
| 8 |
> |
| 9 |
> Before the next Council meeting (ideally a week before, so we've got |
| 10 |
> time to get the questions worked out), I'd appreciate it if every |
| 11 |
> Council member could go through each item on the list below, check its |
| 12 |
> description in PMS (Appendix E has a handy list of links to the |
| 13 |
> relevant text, or look for the boxed labels in the margin) and |
| 14 |
> provisionally mark it as one of: |
| 15 |
> |
| 16 |
> * critical: EAPI 3 needs to be held up until this feature is in Portage. |
| 17 |
> |
| 18 |
> * yes: This feature should be in EAPI 3, but can be dropped if it turns |
| 19 |
> out it's going to take ages to get into Portage. |
| 20 |
> |
| 21 |
> * no: This feature shouldn't be in EAPI 3. |
| 22 |
> |
| 23 |
> * whatever: You have no strong opinion on whether this feature should |
| 24 |
> be in EAPI 3. |
| 25 |
> |
| 26 |
> * query: You have questions about this feature, or you think parts of |
| 27 |
> it need discussion, or you've found a mistake in the PMS draft. |
| 28 |
> |
| 29 |
> I'll try to address any queries as they come so people can update their |
| 30 |
> opinions. |
| 31 |
> |
| 32 |
> I'd also appreciate any review of wording features from anyone else. |
| 33 |
> There are probably still a few holes. |
| 34 |
> |
| 35 |
> Hopefully we can get a final list decided upon and provisionally |
| 36 |
> approved by the next Council meeting, and then as soon as Portage is |
| 37 |
> ready to go we can merge everything into PMS proper and get a signed |
| 38 |
> approval tag as we did for EAPI 2. |
| 39 |
> |
| 40 |
> Here's the list: |
| 41 |
> |
| 42 |
> * PKG-PRETEND |
| 43 |
|
| 44 |
critical |
| 45 |
|
| 46 |
> * SLOT-OPERATOR-DEPS |
| 47 |
|
| 48 |
yes |
| 49 |
|
| 50 |
> * USE-DEP-DEFAULTS |
| 51 |
|
| 52 |
critical |
| 53 |
|
| 54 |
> * DEFINED-PHASES |
| 55 |
|
| 56 |
critical |
| 57 |
|
| 58 |
> * PROPERTIES |
| 59 |
|
| 60 |
critical |
| 61 |
|
| 62 |
> * SRC-INSTALL |
| 63 |
|
| 64 |
query, might not some bikeshedding for the final code |
| 65 |
|
| 66 |
> * CONTROLLABLE-COMPRESS |
| 67 |
|
| 68 |
critical |
| 69 |
|
| 70 |
> * DODOC |
| 71 |
|
| 72 |
yes |
| 73 |
|
| 74 |
> * DOINS |
| 75 |
|
| 76 |
yes |
| 77 |
|
| 78 |
> * ANY-USE |
| 79 |
|
| 80 |
yes |
| 81 |
|
| 82 |
> * BANNED-COMMANDS |
| 83 |
|
| 84 |
yes |
| 85 |
|
| 86 |
> * DOEXAMPLE |
| 87 |
|
| 88 |
yes |
| 89 |
|
| 90 |
> * DOINCLUDE |
| 91 |
|
| 92 |
yes |
| 93 |
|
| 94 |
> * UNPACK-EXTENSIONS |
| 95 |
|
| 96 |
yes |
| 97 |
|
| 98 |
> * ECONF-OPTIONS |
| 99 |
|
| 100 |
yes |
| 101 |
|
| 102 |
> * PKG-INFO |
| 103 |
|
| 104 |
query. I have probably missed what's the use case for non installed |
| 105 |
packages? |
| 106 |
|
| 107 |
> * PROFILE-IUSE-INJECTION |
| 108 |
|
| 109 |
yes |
| 110 |
|
| 111 |
> * AA |
| 112 |
|
| 113 |
yes |
| 114 |
|
| 115 |
> * KV |
| 116 |
|
| 117 |
yes |
| 118 |
|
| 119 |
> * REPLACE-VERSION-VARS |
| 120 |
|
| 121 |
critical |
| 122 |
|
| 123 |
> * S-WORKDIR-FALLBACK |
| 124 |
|
| 125 |
yes |
| 126 |
|
| 127 |
> * UNPACK-IF-COMPRESSED |
| 128 |
|
| 129 |
yes |
| 130 |
|
| 131 |
> * RDEPEND-DEPEND |
| 132 |
|
| 133 |
yes |
| 134 |
|
| 135 |
> * DIE-ON-FAILURE |
| 136 |
|
| 137 |
yes |
| 138 |
|
| 139 |
> * NONFATAL |
| 140 |
|
| 141 |
yes |
| 142 |
|
| 143 |
Regards, |
| 144 |
Petteri |
Archives