Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On 12/04/2011 09:44 AM, Leho Kraav wrote:
> 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:
>
> * move to sys-apps/shadow trunk [6]
> * fork my own user.eclass from v1.17, modify it to use --root $ROOT when calling shadow stuff
I think a possible problem here would be a build system that uses
user/group id's from the host root during the build process. If any
packages do this, it is possible that the users/groups would need to be
added in both /etc/passwd and ${ROOT}etc/passwd.
> * stick my user.eclass into myoverlay/eclass/
> * # echo "lkraav" > myoverlay/profiles/repo_name
> * # echo "[DEFAULT]\neclass-overrides = lkraav" > /etc/portage/repos.conf
> * # echo "PORTAGE_RSYNC_EXTRA_OPTS=\"--exclude=/metadata/cache\"" >> /etc/make.conf
> * # rm -rf /usr/portage/metadata/cache
> * # echo "emerge --regen" >> /etc/cron.weekly/09-my-portage-update-script
That sounds about right.
> * 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
We have one of those!?
|
|
