| 1 |
As some of developers noticed, current gpypi2[0] implementation (tool |
| 2 |
for querying Python Package Index to create ebuilds) needs root |
| 3 |
permissions for two reasons: |
| 4 |
|
| 5 |
- to write ebuild in overlay managed by layman |
| 6 |
- to unpack source for setup.py introspection with "ebuild foobar |
| 7 |
unpack" |
| 8 |
|
| 9 |
It just seems wrong for such a tool for the need of root permissions, so |
| 10 |
I'm asking what are the options to drop layman to root:portage or |
| 11 |
something similar. |
| 12 |
|
| 13 |
Discussion about the approach is open, I'm not *really* sure what would |
| 14 |
be the proper way. |
| 15 |
|
| 16 |
|
| 17 |
Cheers, Domen |
| 18 |
|
| 19 |
|
| 20 |
#0 http://docs.fubar.si/gpypi2/ |
Archives