On Mon, Jan 19, 2009 at 03:14:11PM -0800, [email protected] wrote: > http://cr.opensolaris.org/~comay/webrev-2218/webrev/
Whoof. Why is SUNWDTraceToolkit x86 only? What about the SUNWgetting-started packages? There are others, like SUNWbrasero and SUNWsexy-python, which at least have arch-specific bits in them, but shouldn't be available on both platforms anyway. Do we know why they aren't? Need slim_install be available for sparc at all? Or is it used for AI? Similar question for babel_install. We should probably pull slim_install and babel_install out of slim_cluster and redist_cluster so that we don't have two identical copies of each. Doesn't have to be this wad, though. Doesn't look like you got rid of i386/SUNWmdb? Or is that just an artifact of the way the webrev was generated? (I see the same for SUNWpicl.) For, say, SUNWnxge, can you put only the last line of the driver action under sparc_ONLY? Otherwise, the driver action is exactly the same. In SUNWckr, mpt has a driver action defined. For sparc, mpt is in SUNWpd, but that doesn't have a driver action defined. In both cases, the aliases are in the base driver_aliases file, and not added via postinstall scripts. What's the change to no longer drop libXol from SUNWxwrtl? Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
