| 1 |
On 6/18/2019 7:31 AM, Michał Górny wrote: |
| 2 |
> |
| 3 |
> 3. Give people some time for wider testing. |
| 4 |
> |
| 5 |
> At this point, the new eclasses would be non-binding, i.e. you will |
| 6 |
> still be able to commit new packages using user.eclass old style. |
| 7 |
> The eclasses would be bound with usual eclass stability requirements, |
| 8 |
> i.e. some API changes may happen if necessary. |
| 9 |
> |
| 10 |
> 4. If no major issues arise, submit GLEP 81 for formal approval. |
| 11 |
> |
| 12 |
> Once GLEP 81 is formally approved, using user.eclass directly becomes |
| 13 |
> deprecated and new packages are expected to use acct-*/*. |
| 14 |
> |
| 15 |
|
| 16 |
|
| 17 |
I object to this as some packages just need a user/group for a single |
| 18 |
daemon that is not shared with another package. The numbering does not |
| 19 |
really matter in this case as it will never leave the machine. |
| 20 |
|
| 21 |
user.eclass should exist for this purpose and the acct-{group/user} |
| 22 |
should exist for static purposes which I find to be rather rare. |
| 23 |
|
| 24 |
Brian |
Archives