> I'm feeling challenged this morning... Could someone > please clarify where we stand with regards 20060208? > Specifically as the download section now contains: > > OpenSolaris README (Release Notes) > README.opensolaris 11.56 KB > Full HTML Changelog (with files updated) > on-changelog-20060208.html 54.79 KB > Sparse Text Changelog (CR + synopsis only) > on-changelog-20060208.sparse.txt 3.84 KB > ON Source on-src-20060208.tar.bz2 53.27 MB > Updated SNMP packages necessary for building > update_fma-snmp.tar.bz2 10.69 MB > > Given the last file above, can we now assume that a > full build is possible, based on SXCR 30 (current), > or SXCR 31a (as Karyn said, expected next Tuesday)?
Yes, it is possible, if the build machine is updated with update_fma-snmp.tar.bz2 I've tried it on a snv_28 machine, that was bfu'ed to on-src-20060201 (using quite a few Makefile and /usr/sfw/lib/*snmp* hacks). With update_fma-snmp.tar.bz2 installed, on-src-20060208 compiled cleanly, without Makefile changes. > The readme does not mention the updated fma-snmp > file, and still refers to the need for SXCR build 32 > to achieve a full build. > > Where are we exactly, please? Btw. what happened to the "A. Changes since YYYYMMDD" part of the releasenotes file? In previous opensolaris source releases it contained a hint on the corresponding Solaris Nevada build, for the source drop. Like this: - merged with Solaris Nevada build XX How do we find out which Solaris Nevada build corresponds to the source archive on-src-20060208.tar.bz2? For example, this is needed when filing opensolaris bugs. Neither the downloaded files, nor the download web site contains any hints that could be used to map between source drop date and Nevada build numbers. (or did I miss them?) This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
