It's actually not a trivial question. There was this discussion on pkg-discuss: http://mail.opensolaris.org/pipermail/pkg-discuss/2009-May/013554.html
One of the "secure" Osol/Nv differences I know of are font packages: Nevada: pkginfo SUNWxwfnt (not found on Osol) Osol: pkginfo FSWxorg-fonts-core (not found on Nv) ... Of course this could be temporary, but given the unstability of the -42 repo, I wouldn't worry too much. hnhn Adriaan de Groot wrote: > On Monday 22 June 2009 02:15:32 pm hajma wrote: >> so it seems it's hardcoded there because some of the platform detection in >> the specs doesn't work. In order to proceed on S10/nevada one has to >> remove/modify these > > It would be best to auto-detect the OS. Basically something along the lines of > > %if %(shell test "111b" = `uname -r` && echo 1 || echo 0) > %define %_with_osol 1 > %else > %if %(shell test ... > %endif > %endif > > If we can figre out a decent mapping of uname output to desired platform > build > (or find another way to detect OSOL). The hard-coded bits in there were > because > I was intending to move the -42 repo to IPS packagqes (only). > > [ade] > > > ------------------------------------------------------------------------ > > _______________________________________________ > kde-discuss mailing list > kde-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/kde-discuss -- Jan Hnatek jan.hnatek at sun.com
