Re: pycsw 2.0.0 - proposed package restructuring
Thanks for promoting the release :)
yes, I agree with the plan, sounds good.
On 07/12/2016 12:12 AM, Sebastiaan Couwenberg wrote:
pycsw 2.0.0 is out, and the packaging has been updated and uploaded to
experimental to replace RC1.
With 2.0.0 being a major new release, now is good time to do some
restructuring of the package that is more disruptive.
I propose to remodel it to resemble the pywps packaging more. Have a
pycsw binary package that contains the pycsw-admin executable and
manpage, and have it depend on the python-pycsw package for the Python
module, and on pycsw-wsgi for the the web services. The -doc package
will likewise be renamed to drop the python- prefix.
This restructuring makes the pywps the main package instead of
python-pywps which will become a simple module package without an
executable, and `apt-get install pycsw` should get you a working pycsw
setup via the dependencies.
In support of the move to Python 3 , pycsw should also be built for
Python 3 to at least provide the module via python3-pycsw, and ideally
to use Python 3 for the main pycsw & pycsw-wsgi packages too. In the
Python Policy, the move to Python 3 only contains "should" requirements,
so we don't have to switch pycsw to Python 3 yet, although that's
strongly encouraged via the Policy.
An overview of the proposed restructuring is below, showing what's
installed by the packages and their dependencies.
Johan & Angelos, what do you think of this proposal?
- Package: pycsw
- Package: pycsw-doc
- Package: pycsw-wsgi
- Package: python-pycsw
- Package: python3-pycsw
Angelos Tzotsos, PhD
OSGeo Charter Member