Update on the move from googlecode -> github.
I realized the other day that because github does not automatically generate directory listings for directories, when Ivy was configured to pull from github, it would fail to resolve any module specified with a revision range like "[1.0, 2.0)" because it couldn't get a directory listing.
The workaround is described
here. Basically we have to create a
gh-pages branch for GitHub Pages and auto-generate
index.html files.
The bottom line for committers is this: after committing a change to
master, and regenerating the repository (see
src/scripts/regenrepo.sh) and committing that, please merge the
master branch into
gh-pages as well.
FYI, the old workflow was like this:
- Make changes in src/modules/...
- Commit src/modules
- Run src/scripts/regenrepo.sh to regenerate repo/
- Commit repo/
The idea was to have
$Id$ tags in the repo match the commit, etc. Turns out that was never really useful but whatever.
In any case, with git, there's no reason you can't regenerate the repository as well prior to the first commit.
So the new workflow should now be:
- Make changes in src/modules/...
- Run src/scripts/regenrepo.sh to regenerate repo/
- Commit (master)
- Checkout gh-pages
- Merge master
- Commit (gh-pages)