| 1 |
On Mon, Nov 27, 2017 at 6:46 AM, Aaron W. Swenson <titanofold@g.o> wrote: |
| 2 |
> On 2017-11-26 10:02, Benda Xu wrote: |
| 3 |
>> Hi Patrick, |
| 4 |
>> |
| 5 |
>> Patrick McLean <chutzpah@g.o> writes: |
| 6 |
>> |
| 7 |
>> > I use portage as non-root all the time when developing and testing |
| 8 |
>> > ebuilds, via the "ebuild" command. |
| 9 |
>> |
| 10 |
>> The enewgroup and enewuser are used in pkg_* functions, as documented in |
| 11 |
>> user.eclass _assert_pkg_ebuild_phase() function. They require root to |
| 12 |
>> execute. |
| 13 |
>> |
| 14 |
>> So no worries, your workflow will not be affected. |
| 15 |
> |
| 16 |
> Actually, it will probably be better. |
| 17 |
> |
| 18 |
> You should now be able to do compilation and tests without having the |
| 19 |
> user/group created. For example, dev-db/postgresql doesn’t need the |
| 20 |
> postgres system user and group in order to successfully run through |
| 21 |
> src_test and src_install. It just needs the user/group at run time. |
| 22 |
|
| 23 |
Sounds like the enewuser call should be moved from pkg_setup to |
| 24 |
pkg_postinst in that case. |
Archives