On 11/27/2017 10:16 AM, Mike Gilbert wrote:
> On Mon, Nov 27, 2017 at 6:46 AM, Aaron W. Swenson
> wrote:
>>
>> You should now be able to do compilation and tests without having the
>> user/group created. For example, dev-db/postgresql doesn’t need the
>> postgres system user and group in order to
On Mon, Nov 27, 2017 at 6:46 AM, Aaron W. Swenson wrote:
> On 2017-11-26 10:02, Benda Xu wrote:
>> Hi Patrick,
>>
>> Patrick McLean writes:
>>
>> > I use portage as non-root all the time when developing and testing
>> > ebuilds, via the "ebuild" command.
>>
>> The enewgroup and enewuser are used
On 2017-11-26 10:02, Benda Xu wrote:
> Hi Patrick,
>
> Patrick McLean writes:
>
> > I use portage as non-root all the time when developing and testing
> > ebuilds, via the "ebuild" command.
>
> The enewgroup and enewuser are used in pkg_* functions, as documented in
> user.eclass _assert_pkg_eb
Fabian Groffen writes:
> I think we could definitely live with this until someone requests
> otherwise.
Indeed.
Committed, thanks a lot!
Benda
signature.asc
Description: PGP signature
Hi Patrick,
Patrick McLean writes:
> I use portage as non-root all the time when developing and testing
> ebuilds, via the "ebuild" command.
The enewgroup and enewuser are used in pkg_* functions, as documented in
user.eclass _assert_pkg_ebuild_phase() function. They require root to
execute.
On 21-11-2017 20:19:21 +0900, Benda Xu wrote:
> Francesco Riosa writes:
>
> > maybe ewarn() is more appropriate than einfo()?
> > Just in case it's executed outside the scope of prefix
>
> I can't remember any use case when portage (or, paludis, etc.) is
> executed as a normal user but not a fro
On 2017-11-21 03:19 AM, Benda Xu wrote:
> Francesco Riosa writes:
>
>> maybe ewarn() is more appropriate than einfo()?
>> Just in case it's executed outside the scope of prefix
>
> I can't remember any use case when portage (or, paludis, etc.) is
> executed as a normal user but not a from Pref
Francesco Riosa writes:
> maybe ewarn() is more appropriate than einfo()?
> Just in case it's executed outside the scope of prefix
I can't remember any use case when portage (or, paludis, etc.) is
executed as a normal user but not a from Prefix.
This message will only affect Prefix users, who w
Francesco Riosa writes:
> maybe ewarn() is more appropriate than einfo()?
> Just in case it's executed outside the scope of prefix
I can't remember any use case when portage (or, paludis, etc.) is
executed as a normal user but not a from Prefix.
This message will only affect Prefix users, who w