[Zope-CMF] CMF 3.1 doesn't install on zope 2.6.1

[Josef Meile]

> CMF should be packaged like it is now, with a folder containing the
release
> with an appropriate version number in the folder name.  On platforms with
> symlinks, it makes non-destructive, quick, undo-able upgrades easier the
way
> it is packaged now:
>
> i.e.:
> cd lib/Python/Products
> tar xvfz CMF-1.3.1.tgz
> ln -s CMF-1.3.1/CMFCore .
> ln -s CMF-1.3.1/CMFCalendar .
> ln -s CMF-1.3.1/CMFCTopic .
> ln -s CMF-1.3.1/CMFDefault .
> #restart Zope
> #a few months later:
> cd lib/Python/Products
> tar xvfz CMF-1.4.tgz
> rm CMFCore CMFCalendar CMFTopic CMFDefault
> ln -s CMF-1.4/CMFCore .
> ln -s CMF-1.4/CMFCalendar .
> ln -s CMF-1.4/CMFCTopic .
> ln -s CMF-1.4/CMFDefault .
> #restart Zope
>
> Reverting back is simply a matter of changing symlinks and restarting Zope
> in the 'Doh! this upgrade broke something' scenario.  Under the status
quo,
> Windows users would still have to settle for some dragging-and-dropping in
> Windows Explorer.
>
> Sean
Yes, you're right! For linux users it's really easy to have two versions of
CMF in
the same machine and revert the changes if something goes wrong.
Unfortunatelly,
windows users would have to delete the new version and restore the old one,
but I guess it's not that difficult.

Thanks,
Josef.