On Sun 03 Aug 2008 at 08:00PM, Danek Duvall wrote:
> On Sun, Aug 03, 2008 at 08:03:58PM -0700, Dan Price wrote:
>
> > pkgsend/pkg5: Do group actions sort before user actions? It's
> > not clear from the text what the correct way to deliver a group
> > and user whose primary group is that group, in the same package.
>
> Ordering in a manifest is irrelevant. Actions (across manifests) get
> sorted properly at install or removal. Feel free to dump 'em in in any
> order you like (though some consolidations may choose to put constraints on
> manifests for the sake of maintainability).
I know that, but if you read the text, it's not at all clear:
161 + user username=<username> password=<password> uid=<uid> \
162 + group=<group> gcos-field=<gcos> home-dir=<homedir> \
163 + login-shell=<login-shell> group-list=<groups> \
164 + ftpuser={true|false} lastchng=<lastchange> min=<mindays> \
165 + max=<maxdays> warn=<warndays> inactive=<inactivedays> \
166 + expire=<expiredate> flag=<flag> [ property_list ]
167 + Deliver a user account, as defined in passwd(4), shadow(4),
168 + group(4), and ftpusers(4). If the user ID, or uid, is
169 + omitted, then the first free user ID under 100 will be
170 + assigned at installation time. The primary group,
specified
171 + by group, must exist prior to the action's execution. See
172 + pkg(5) for additional details.
The user is left to wonder... "how do I ensure that the primary group
exists prior to the actions execution?"
It might be clearer to say: the primary group must be defined by
a group action provided either by the same package, or by a package
upon which the package expresses a dependency.
-dp
--
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
