Conversation
Alternative approach to #450
|
@drfho This approach does work as well. I have successfully built and deployed
Note If the In this |
My test-case shows that the ordinary -e-install in Zope5.13 still needs setup.py. If setup.py the installation is only stable with: pip install Zope[wsgi]==$ZOPE_VERSION -c https://zopefoundation.github.io/Zope/releases/$ZOPE_VERSION/constraints.txt
pip install -r https://raw.githubusercontent.com/zms-publishing/ZMS5/main/requirements-full.txt
pip install --use-pep517 --config-settings editable_mode=compat -e git+https://github.com/zms-publishing/ZMS.git@zms6a#egg=ZMS
I revised the branding/program-version by utilizing the description package/project-data for down-compatibility and a late merge with latest ZMS5: 34a71f4 |
I cannot confirm this @drfho -> there is no ...and I used this to install ZMS6a on top of these base images: After removing the symlink approach in this branch and introducing |
@cmeier76 : thanks for the feedback. You are right, the parameter |
|
@zmsdev, @cmeier76 Besides some minor docker customisations for switching the Zope-versions, the code status of this branch introduces only two aspects:
So, actually here is no specific change that makes ZMS exclusivly run on Zope6: means, an existing traditional editable-installation with Zope5 on a host after will still run after simple code-update by git-pull (both ZMS5 and 6 ). Tasks:
|


This is an alternative approach to #450 without the huge diff in the git,
Goal is to be compatible with Zope5 and 6.