Re: [gentoo-dev] user management mitigation

[Leho Kraav <leho@kraav.com>]

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
 * 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
 * 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
 * try to achieve clamlike happiness with this setup

Anything particularly important I'm missing? Is this the rightish way to do it?

 [1]: https://forums.gentoo.org/viewtopic-p-5877500.html
 [2]: https://groups.google.com/forum/#!topic/linux.gentoo.dev/FYJ4g5IryIw/discussion
 [3]: https://alioth.debian.org/tracker/index.php?func=detail&aid=312407&group_id=30580&atid=411480
 [4]: https://bugs.gentoo.org/show_bug.cgi?id=53269'
 [5]: http://www.linux-archive.org/gentoo-embedded/295178-emerge-root-users-not-created.html
 [6]: https://bugs.gentoo.org/show_bug.cgi?id=393073