Adding r.User() and r.Group() invocations in package recipes was made possible in Conary relatively recently, but it means that info-* packages keep getting updated on systems, which has no benefit and some cost.
Also, it's been hard to keep track of all the system users that exist for creating new users where the IDs do not overlap. I finally did something to make it easier. https://wiki.foresightlinux.org/wiki/display/DEV/Creating+Users+and+Groups This documentation could be expanded and improved, but here's what it says so far: In order to keep user and group information consistent across foresight, all user and group information is now maintained in a single superclass: foresightinfopackage To add a new user/group, edit foresightinfopackage.recipe and put the user or group in the appropriate list, sorted by the numeric ID (uid/gid) to make it easy to find available system users. Use IDs less than 500 for all system users. Commit your change to the superclass. Then create an info package: loadSuperClass('foresightinfopackage') class InfoSomeuser(ForesightInfoPackage): name = 'info-someuser' version = '1' That package will use the user definition from the superclass, keeping things synchronized. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
