On 3/18/10 16:17 , Radim Novotny wrote:
Hi all,
I'm wondering how to handle add-on package versions if package is
different for Plone 3 and Plone 4.
Situations:
1) dependencies - package requires some add-on which is obsolete in
Plone 4, eg. collective.js.jquery - this adds jQuery 1.3.2 which is in
Plone 4 by default. I don't want this package installed if my package is
installed on Plone 4
2) separate versions for Plone 3 and Plone 4 - for example: I want to
release the same package for Plone 3 only and for Plone 4 only. How
should I declare dependencies ? How should I tell users my.package 1.x
is for Plone 3 and 2.x for Plone 4 only ?
A simple trick is to test the python version, and modifiy your
requirements list based on that. Chances are that if someone uses
python2.4 you are dealing with Plone 3, and python 2.6/2.7 can only be
Plone 4.
Wichert.
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
