> I would like this Rod but I am afraid I am long away from an
> understanding of your build/commit/release etc processes. E.g. the
> openslug 3.10 beta tarball would not build for me (I whittled it down to
> insurmountable tar and permission errors etc). I did a svn co
> and that surprisingly built fine (I would have thought "releases" was
> analogous to an svn tag - but there were 67 newer commits in there?
We release from monotone to the svn releases branch, and then maintain
the stable release from there (while monotone progresses into an
> And where is this "4th" method of building from source documented? I
> just fluked finding it from a passing comment in the forums!).
> Would developer access allow me to commit to that svn tree, or would I
> have to wrestle with monotone?
You would be committing to monotone - only the SlugOS package manager
(Oyvind) commits to the stable releases branch.
> BTW, building the latest head unslung 6.8 svn sources fails with the
> same tar and permission errors I get with the openslug tarball. Has
> the fix for that not been propagated to the unslung svn release tree?
Dunno - we haven't had to touch that since releasing it.
> I find the documentation somewhat piecemeal, esp given various
> alternative firmwares about which I still can't really discern the
> essential differences or advantages. Is it expected that there is a
> bit of a steep learning curve to all this stuff, or am I just showing
> my age? :(
Use the MasterMakefile - "make openslug-3.10-beta" if you want to start
with a stable release. That should always build.