Packages for all systems about crunchy HOT 18 OPEN

As an addendum: the python community would probably like a .egg file too.

On a OSX, we can use py2app to create a proper Mac Application - one that users 
can
D&D to their Applications folder.

In order to make some progress with this I am writing some release scripts to 
pull a
release from SVN an automatically package it up.

I will start by writing a simple script that will create .zip and tar.gz 
archives.

In order for these scripts to work they will need the release to be tagged.

The script will take as an argument the release version and look in
http://crunchy.googlecode.com/svn/tags/$version$

Ok, the script is in the repository at trunk/tools.

In order to use it you need to copy over the code you want to use into a tag - 
and
make sure the folder name is the version number. Then run the script, giving it 
the
version number.

This automatically pulls the data out of SVN, zips and tars it up. Then you can
upload through the GUI on the site.

OK, now that we have a script up and running we just need to decide which 
packaging
formats we want to target.

I vote for:
 * Apple Universal Application (OSX)
 * deb (Ubuntu, Debian and derivatives)
 * rpm (Fedora and the olpc)
 * Some kind of windows installer (easyinstall, NSIS or py2exe based)
 * zip and tar.gz to keep the techie people happy

Any more needed?

In spite of what I wrote on issue 108, I think it would be preferable (if we can
easily) to also include an egg version that can be loaded via easy_install.

We should do some internal tests and have the first "public release" targeted 
for 1.0
Release Candidate 1  (or Beta 1?), asking for feedback about the various 
installers.

For Windows, I would think NSIS -based on a very limited end-user experience.

I've now got a working mac .app

This really was surprisingly little work :)

We should also see if Paver[1] can help at all - it has SVN integration and 
seems to
be a more general solution tha setuptools.

[1] - http://www.blueskyonmars.com/projects/paver/

Its time to look at which platforms we want to target for the 1.0 release. It 
would
take too long to implement all the packages mentioned above (deb and rpm are
particularly complex) so I suggest we ad in some kind of windows package for 
release 1.0.

Sadly (or maybe not...) I don't have a windows machine at the moment, so 
someone else
will ahve to figure out how to do this.

I have created a simple windows installer using NSIS. Could someone with a 
windows
installation please test it out - the file is attached.

I have tried the exe version. It has the following problems:

1. only the top files (crunchy.py, all_tests.py, license, etc) and  none of the
subdirectories ( src, etc.) are included.  This means that it does not work.
2. All files are simply copied to an obscure subdirectory, hidden, therefore
unaccessible for a "normal user".
3. No shortcuts or menu items are created.

I believe that Tao has started on an improved crunchy.nsi version. I have not 
tried
the version attached to comment 11.

I think its worthwhile resurrecting the windows installer subproject, as well as
trying to create a .app package for macs. Most linux users are happy to take 
archives
and unpack them themselves, but mac and windows users like things to work in the
"standard" way.

I agree :-(   More work to do before the 1.0 release - and something that has 
to be
done as the very last step, but it is something worthwhile.

I'm away on holiday for the next couple of weeks, but when I get back I could 
take a
look at the windows installer. Seems like a good way of seeing what's changed.

I've release the 1.0 version without the installer.  I'm waiting to get some 
feedback
before looking into creating some installers.

I am working on this. I have refactored crunchy to use setuptools. The code can 
be
found in the jdjolonga branch. Doing a simple python setup.py install and then
crunchy-server.py has been tested and works on both Ubuntu 9.10 and Windows7. I 
have
successfully generated rpm, a dumb tar and a Windows installer. One possible 
problem
is that bdist_wininst does not automatically pull the dependencies (i.e. 
pygments)
from PyPI. I will try to come up with a solution.