I've updated all the masters and devels to
- integrate a round of cleanup removing files no longer necessary.
- the latest changes from SVN.
I've also adapted the test-suite (in bro-private) to work with the
new setup, and it passes fine with all the changes (well, to be
precise, it reports the same differences as svn trunk; seems it's
not completely up to date).
We should now see if master is working for everybody. If so, we'll
have a stable base to work from.
Robin
We should now see if master is working for everybody.
If you want to merge topic/cmake-port across the board into master again there's fixes to add CMake 2.6 compatibility and remove the fiddling of install_name on optional darwin libs.
- Jon
Done (and into devel).
The merging is really easy. Updating the submodules is somewhat
cumbersome, but perhaps I haven't found the right recipe for doing
all of them at once yet (I'm already using "git submodule foreach"
but still).
Robin
PS: I've installed a new commit notification script which for now is
sending just to me. If it works fine, I'll remove the old one and
switch over.
The merging is really easy. Updating the submodules is somewhat
cumbersome, but perhaps I haven't found the right recipe for doing
all of them at once yet (I'm already using "git submodule foreach"
but still).
That's the best way I found; I don't think it will be that bad after things settle down and we don't need to make these updates that span all repositories.
Can you re-check that the broccoli/master repository has an updated submodule for broccoli-python; it didn't look like it was using the master version of broccoli-python.
- Jon
Updated.
Robin