[schooltool-dev] Eggs, Tarballs and Packages

[Brian Sutherland]

Quite some thing have happened all of a sudden with the way schooltool
is distributed/structured.

So, I guess I should just explain what happened:

    * Made a branch that releases schooltool as an egg
        http://svn.schooltool.org/schooltool/branches/schooltool-eggs-redux/
    * Made nightly releases from that branch as an egg
        http://ftp.schooltool.org/schooltool/releases/nightly/
    * Made a buildout installer (thanks ignas!!!)
        http://svn.schooltool.org/schooltool/trunk/st-buildout/
    * Made a schooltool and python-schooltool package based on the egg
        deb http://ftp.schooltool.org/schooltool/archives/debian/ unstable main

The schooltool package doesn't install (missing dependencies) and is
probably broken in many other ways, but is very useful as a proof of
concept.

The buildout installer seems to work great, and can easily produce a
running schooltool server. But I think it needs to be banged on a bit to
make it run on other os'.

So this sets up a lot of the infrastructure that we need to be able to
make package releases. Thinks are not perfect yet, there are some
notable exceptions:

    * Translations are not built in the egg (should they be?, can 
      you do this in pure python?)
    * There are lots of eggs we depend on that still need to be
      converted to debian packages (help!).
    * How's CanDo going to adapt to this change, the eggs-redux branch
      does totally break their release infrastructure.

On the whole, I'm quite happy with what we've done. It gets rid of a lot
of the remaining nastiness in the release infrastructure and it looks
like we can actually make releases this way.

I'd like to propose merging the schooltool-eggs-redux branch. Any
objections? Can someone from CanDo comment? 

-- 
Brian Sutherland