| 1 |
On 12/04/2011 09:44 AM, Leho Kraav wrote: |
| 2 |
> So after a reading through a bunch of stuff [1][2][3][4][5], what I'm going to do for the goal above is: |
| 3 |
> |
| 4 |
> * move to sys-apps/shadow trunk [6] |
| 5 |
> * fork my own user.eclass from v1.17, modify it to use --root $ROOT when calling shadow stuff |
| 6 |
|
| 7 |
I think a possible problem here would be a build system that uses |
| 8 |
user/group id's from the host root during the build process. If any |
| 9 |
packages do this, it is possible that the users/groups would need to be |
| 10 |
added in both /etc/passwd and ${ROOT}etc/passwd. |
| 11 |
|
| 12 |
> * stick my user.eclass into myoverlay/eclass/ |
| 13 |
> * # echo "lkraav" > myoverlay/profiles/repo_name |
| 14 |
> * # echo "[DEFAULT]\neclass-overrides = lkraav" > /etc/portage/repos.conf |
| 15 |
> * # echo "PORTAGE_RSYNC_EXTRA_OPTS=\"--exclude=/metadata/cache\"" >> /etc/make.conf |
| 16 |
> * # rm -rf /usr/portage/metadata/cache |
| 17 |
> * # echo "emerge --regen" >> /etc/cron.weekly/09-my-portage-update-script |
| 18 |
|
| 19 |
That sounds about right. |
| 20 |
|
| 21 |
> * subscribe to atom feed of portage user.eclass changes, merge stuff until sys-apps/shadow-4.1.4.5 surfaces and maybe main tree user.eclass gets patched to use --root |
| 22 |
|
| 23 |
We have one of those!? |
Archives