On 2013-01-27 16:46, Jim Klimov wrote:
What I'd expect to see ultimately is a number of steps like these: * bootstrapping the build environment(s), i.e. under current OI * checking out current gates of incorporations (right term?) like kernel illumos-gate, and userspace oi-build(?), jds, sfe... * building the lot * making a bootable distro image with desired contents and an IPS (SVR4, DEB, .....) package repo for other optional software
Also, the illumos-gate docs suggest using a larger version number for private builds to override the published common packages - i.e. 152
while OI is 151. I do also see that nested version numbers are used, i.e. 0.151.7 for oi_151a7 release. Is it allowed (and will it give the logically correct result) to add more levels, i.e. 0.151.7.1 for a private build with local patches applied to the 151a7 release's source codes as a baseline, 0.151.7.2 for the private build's respin, etc? As part of "preparing build envs" above, the versioning games should also be discussed, if needed (what, where, how)... Thanks, //Jim _______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
