[email protected] wrote: >> Whoof. > > Thanks for the review! > >> 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? > > In most if not all of the cases, it's because the consolidations in > question haven't delivered them. Some of them like SUNWDTraceToolkit > just need to get built/repackaged (that one in particular could have > ARCH=all) but others may have some longer-term dependencies that need > to be addressed (such as the Compiz-related ones). > > My expectation is that we'll be addressing this over time but some of > them should be fixed shortly. >
We can redeliver an 'all' SUNWDTraceToolkit at any time, I've made the change to the sources. >> Need slim_install be available for sparc at all? Or is it used for AI? >> Similar question for babel_install. > > The AI team requested we supply them for now although I expect there > will be other clusters created in the future. > >> 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. > > Okay. I've been wanting to get rid of this duplication for awhile now > but I know the slim_cluster is still used by the Live CD folks for > testing purposes (haven't tested import times with recent bits to see > how much longer a full reditributable import takes). I'll open up a > bug about this. > It's more than twice as long. I'd be happy to see less duplication, but please don't just drop the slim import capability. Dave _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
