Installing archgenxml 
=====================

From the cheeseshop
-------------------

``easy_install archgenxml``, so the usual.


From tgz
--------

To install it use the --no-compile option for now. We need to figure out how
to exclude dtml-files ending with .py from byte-compiling at install time.::

  $ python setup.py install --no-compile


At Debian based systems
-----------------------

To build a Debian Package run::

  $ fakeroot debian/rules binary
  
and install the *.deb file as usal.



SVN directories - what is stable, what is not?
----------------------------------------------

ArchGenXML's svn trunk has been changed to be the 2.x development
version. The stable version is in the 1.5 branch.

As usual, the goal is to keep trunk workable. Some of the developers
work and develop on the edge: trunk. 

If you need stability, use the latest release.

Major changes in 2.0
--------------------

We updated ArchGenXML and changed tons of things to get modernized generated
code.

As a warning: Using an old model with ArchGenXML 2.0 creates some work. This
specially if you ave lots of logic in AppInstall.py or custom workflow scripts. 
You need to migrate such code manually.


Installing trunk
----------------

With 1.6, we switched to using setuptools. So you can use the familiar
"python setup.py install" to install from subversion.

It is probably handier to do "python setup.py develop", though, as
that wires up your svn checkout as the currently installed
version. This is the almost-no-hassle way recommended for those that
run from svn trunk.

"python setup.py install" (or develop) generates and installs an
"archgenxml" script in /usr/local/bin or wherever your python uses to
place its executable scripts. The big advantage is that this works
well on windows, too.

OSX note: This can be a funny location on OSX. I know that I've had to
look around quite a bit. If it is a funny location, just symlink it
from somewhere in your path.


Dependencies
------------

ArchGenXML has a dependency on some zope3 machinery. It requires you to
have a zope 3.3 or zope 2.10 lying around somewhere. We'd love to do
this with eggs, but that messes up other zopes that use the same
python version. And zope is only half-half eggified.

So just start "archgenxml" and it'll complain about not finding some
zope libraries and it'll give you instructions on how to handle
that. If somebody's got a better idea that doesn't mess up all sorts
of things: please open a bug in the issue tracker.

Dependencies are: zope.interface, zope.component and zope.configuration.


