<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>[resend with updated information]</div><div><br><blockquote type="cite"><div>I started 2 open groups on LaunchPad.net<br><br><a href="https://launchpad.net/">https://launchpad.net/</a>~rodents For those interested in collaborating on Cuis and derived images.<br><a href="https://launchpad.net/">https://launchpad.net/</a>~smalltalkers - For anyone else.<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><br></div><div>Launchpad uses Bazaar2.0, I liked git for 1 day, but github doesnt offer open repositories, or open team projects, so it is back to the old faithful bazaar! Launchpad.net is very cool though.</div><div><br></div><div>We have two projects so far</div><div><br></div><div><a href="https://code.launchpad.net/cuis">https://code.launchpad.net/cuis</a></div><div><div><a href="https://code.launchpad.net/cuis-packages">https://code.launchpad.net/cuis-packages</a></div><div><br></div></div><div>To use - begin by making yourself a local working directory...</div><div><br></div><div># mkdir Cuis2.0_trunk</div><div># cd Cuis2.0_trunk</div><div><br></div><div>Runtime and One-Click template</div><div>=========================</div><div>Checkout the vm runtime - this is also a one-click image template for you to branch from, or help improve.</div><div><br></div><div># bzr branch <span class="branch-url">lp:~rodents/cuis/Cuis2.0vm.app</span></div><div><br></div><div>Incremental Kernel Development</div><div>==========================</div><div>Checkout the current Cuis2.0 kernel development repositories - these are the starting image and InstallStreams for incrementally moving the kernel forwards.</div><div><br></div><div># bzr checkout --lightweight <span class="branch-url">lp:~rodents/cuis/base</span></div><div># bzr branch <span class="branch-url">lp:~rodents/cuis/release</span></div><div><div><div><div># bzr branch <span class="branch-url">lp:~rodents/cuis/stable</span></div><div><div># bzr branch <span class="branch-url">lp:~rodents/cuis/unstable</span></div><div><div><br></div></div><div><div>1) cuis/base - the starting image to build on using InstallStreams</div><div><br></div><div><div>To check out Juan's original official release, rather than the most recent.</div><div># bzr checkout --lightweight -r tag:Cuis2.0-0393 lp:~rodents/cuis/base test</div><div><br></div></div><div>2) cuis/release - the released updates (included in the release image)</div><div>This is intended to track Juan's official updates, which are tagged.</div><div>It also tracks ./base/Cuis2.0.1,image showing what it contains.</div><div><br></div><div><div>3) cuis/stable - branch & contribute back your tested updates here</div><div>In anticipation that these may get incorporated in the release by Juan.</div><div><div><br></div><div>4) unstable - branch & contribute your "being-tested" updates here</div><div><br></div><div>Unstable patches are not built by default.</div><div><br></div><div>The default search for updates is only 2 directories deep. In the unstable repository each contributed set of updates is published in a containing folder, and is 3 levels deep, escaping the standard search</div><div><br></div><div><div>"To apply a specific unstable update execute:"</div><div>InstallStreams updatesInstall: 'unstable/InstallStreams-testing'.</div><div><br></div><div>"To apply all unstable updates execute"</div><div>InstallStreams updatesInstall: 'unstable'.</div></div><div><br></div><div><div>Optional Kernel Innovations Development</div><div>=================================</div><div>InstallStreams providing optional kernel innovations may go in their own repositories, rather than release,stable, or unstable.</div><div><br></div><div>i.e. when you are ready to show the world...</div><div><div># bzr push <span class="branch-url">lp:~rodents/cuis/simple-namespaces</span></div><div></div></div></div><div><div><div><div># bzr push <span class="branch-url">lp:~rodents/cuis/pragmas</span></div><div></div></div></div></div><div><div><div><div><div># bzr push <span class="branch-url">lp:~rodents/cuis/nano-traits</span></div><div># bzr push <span class="branch-url">lp:~rodents/cuis/logging</span></div><div><br></div><div></div></div></div></div><div>Packages - Loadable with InstallStream</div><div>===============================</div><div>There is a separate project for sharing loadable packages. </div></div><div>In your working directory make a sub-directory for non-installed packages,</div><div>and checkout/branch your chosen packages there.</div><div><br></div><div># mkdir packages</div><div># cd packages</div><div># bzr checkout lp:~rodents/cuis-packages/Installer</div><div><br></div><div>To manually load an individual package</div><div>InstallStream packagesInstall: 'packages/Installer'</div><div><br></div></div></div></div></div></div></div><div><div>To manually install all the packages you have checked out into ./packages</div><div><div>InstallStream packagesInstall: 'packages'</div><div><br></div><div>Generating the build</div><div>================</div><div>Juan's original release of Cuis2.0 does not appear to support the execution of a script on start up. So I have provided a modified image for you to begin with, this is called: (I should have called it 2.0.1-build or something less official looking, however if Juan doesn't mind, I will leave it as it is)</div><div><br></div><div>Cuis2.0.1.image</div><div><br></div><div>A simple script is provided in ./stable/build.sh which copies the ./base directory into your working directory giving you a known starting point, and then launches the image with ./stable/build.st. (on mac only for the moment)</div><div><br></div><div><div>A second simple script is provided in ./unstable/build.sh which launches the image with ./unstable/build.st. </div></div><div><br></div><div>enjoy</div><div><br></div><div>Keith</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><div><br></div></div><div><br></div><div><br></div><div><br></div></div></div></div><div>
<div id="upload-directions">
<dl id="upload-url">
<dt></dt></dl></div></div></body></html>