Craig Mohrman wrote: > I'll still be very cautious about possible differences between the > versions so I'll still need to use gmake sample-manifest or compare the > proto areas to ensure they have the same relative content. > > Is it possible to handle potential differences in the proto areas in a > single manifest?
It is possible, but I haven't integrated any support for it, since I haven't seen the need yet. There are two mechanisms that you can use. You can tag actions that are specific to a particular set of versions, and drop those actions with pkgmogrify if we're working with a manifest that's not for one of those versions. This is similar to how Userland deals with x86 vs sparc. The other way is to have a set of macros whose names are derived from the runtime and its versions that evaluates to a comment character, and put the appropriate one(s) at the beginning of the line(s) of an action that doesn't belong in all versions. This is similar to how ON deals with architecture-specific files. Either way is pretty straightforward to add at a later point, though I'll note that getting two alternatives to work is easier than three or more. Thanks, Danek _______________________________________________ userland-discuss mailing list userland-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/userland-discuss
