It is nice that there is a flux of changes in woof.
I was wondering however if we should open a "testing branch" where the new commits can go, test that they allow building a sane puppy and then move to master.
Alternatively we can use the WCES(woof community edition stable)-number tag to indicate commits that are tested to build a _sane_ puppy.
The idea behind it is that will be very hard for a newcomer or even a developer to work with a constantly moving git HEAD
So what I think is that someone should build in regular intervals the last puppy build from BK's tree, ie Precise, release it under Precise-testing-WCES#, verify that they are _no regressions_ and then pull to master or mark with WCES. In the second case only commits that fix the regressions would be allowed in (the single) master branch.
When a "stable" release is made, then that can be used for regression testing instead of Precise-5.7.1
Thoughts ? Hmmm ...
I still have to learn what words like fork, branch, tag, ref, head and so forth exactly mean and how to work with them.
About building from woof : I have not used woof until now, just fired up the gui several times and downloaded woof few times "just in case" and looked into the expanded tar balls . Am also on a 5GB/month full-speed internet limit, so not too much interested in downloading binary packages from whatever repository all the time .
You know, you can essentially build everything yourself and keep your own local repository inside the woof tree... you don't need a full featured distro, just build it with essentials, will preserve your fragile download limit.
I found the conflict by merging master with testing then pushed testing and then master, so it worked out in the end. Karl, your issue might be more fun since you have several of your own commits. Iguleder might be able to help.