On Thu, 22 May 2008, Felix Schwarz wrote:
I really want to use PyLucene. Unfortunately, it is very hard to package the
software well due to (at least) two issues:
1. Please don't use version numbers with '-', e.g. 2.3.2-1. RPM does not
allow such version numbers as '-' is the separator for the RPM release.
What about 2.3.2.1?
The version is defined in the Makefile with the VERSION variable. You're
welcome to change it to whatever you'd like at build time as in:
make VERSION=2.3.2_1 ...
2. Please provide a separate download for jcc (even if you like to include it
in the main PyLucene package). Then I don't have to include the quite big
source tar.gz into two RPM packages.
You can get JCC separately from cheeseshop [1] or from svn [2][3].
Do you think implementing the proposals above will have other negative side
effects I did not think of?
I don't know, I don't use RPM so I don't really understand what the problems
are that you're facing. If RPM wants to own the letter '-' then, no worries,
change the version name to whatever works in your context. If you think the
sources of PyLucene and JCC should be separate, then after unpacking the
source tar, rm -rf jcc, or better yet, get what you need and want from the
PyLucene subversion repository [4][5] and customize things to your needs.
Andi..
[1] http://pypi.python.org/pypi/JCC/1.9
[2] http://svn.osafoundation.org/pylucene/trunk/jcc/jcc/
[3] http://svn.osafoundation.org/pylucene/branches/release-2.3/jcc/
[4] http://svn.osafoundation.org/pylucene/trunk/jcc/
[5] http://svn.osafoundation.org/pylucene/branches/release-2.3/
_______________________________________________
pylucene-dev mailing list
pylucene-dev@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
