| 1 |
On 2017-11-21 03:19 AM, Benda Xu wrote: |
| 2 |
> Francesco Riosa <vivo75@×××××.com> writes: |
| 3 |
> |
| 4 |
>> maybe ewarn() is more appropriate than einfo()? |
| 5 |
>> Just in case it's executed outside the scope of prefix |
| 6 |
> |
| 7 |
> I can't remember any use case when portage (or, paludis, etc.) is |
| 8 |
> executed as a normal user but not a from Prefix. |
| 9 |
> |
| 10 |
> This message will only affect Prefix users, who won't be surprised that |
| 11 |
> they cannot create new groups or users. Therefore I think einfo is more |
| 12 |
> appropriate. |
| 13 |
> |
| 14 |
> |
| 15 |
> Furthermore, we do have Prefix that runs as a root, mostly usable on NAS |
| 16 |
> or smartphones, when we do ultimately like portage to manage groups and |
| 17 |
> users. |
| 18 |
|
| 19 |
I use portage as non-root all the time when developing and testing |
| 20 |
ebuilds, via the "ebuild" command. |
Archives