* Tom Mueller (pkg-discuss) <tom.muel...@sun.com> [2009-03-23 22:09]: > In preparation for fixing issue 870 can we establish a convention for > defining an operating system variant for an action? > > I'd like to propose: > variant.os = ["sunos" | "linux" | "windows" | "darwin"] > > The values for this variant are from the Python platform.system().lower(). > > These variant values would then be used to implicitly tag actions that > are platform specific, e.g., a driver action would implicitly have the > "variant.os=sunos" tag. A link action would have "variant.os=sunos > variant.os=linux variant.os=darwin". By implicitly, I mean that the code > for that action would add those variants to the action at runtime. The > list of actions that would have this includes: > > driver: sunos only > legacy: sunos only > hardlink: sunos, linux, darwin > link: sunos, linux, darwin > > I'm not sure what to do about user and group because these really only > make sense for a full image, not a user image. They certainly don't > apply to Windows. > > The variant.os value will be set in Image.load_config and > Image.set_attrs as is currently done for variant.arch.
870 is about image contexts, not OS contexts. We're not doing variant.os, for all the reasons previously discussed. If you'd like to talk about variant.image-type, that would be appropriate. Danek was wondering if user images needed to have a subtype, I think. - Stephen -- s...@sun.com http://blogs.sun.com/sch/ _______________________________________________ pkg-discuss mailing list pkg-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
