> On 02/29/2012 09:39 PM, Ryan Leavengood wrote: > > Another idea I have been thinking about to lower the barrier to > > entry > > into Haiku development is a VirtualBox VDI which is already set up > > as > > a Haiku development machine with a recent known to work revision, > > the > > necessary (and up-to-date) build tools, and an anonymous Git copy > > of > > the source (maybe not checked out to save space.) It could also > > include tutorials and start up guides which show up on the first > > run, > > useful Desktop shortcuts, etc. > > You mean pretty much like the nightlies? > > While I like the basic idea, I'm not sure it really worth the effort. > You probably don't want to lose all your work every time you update, > so > you will want to put the important stuff (like the sources) on a > second > drive image, anyway. > What needs to be on there then? Who is to select the 'good' > revisions? > > Bye, > Axel. > haha, just had a similar problem discussion, someone here at the uni wanted to try to develop on haiku in virtual box. Alex and I suggested to have two images, one with the haiku OS and one with the source/data. Maybe provide nightlies with the dev tools (if not already included) and write a small tutorial how to include a second data image. We could also provide this second image just with a script that download the source and all missing parts like git and maybe even starts compiling everything... Will look into it, this could also be handy for a student project that starts tomorrow :) Regards, Clemens