Alan Conway wrote:
Your use of "incubating-M3" as a version number is choking rpmbuild.
QPID_PYTHON_DIR=/usr/share/cruisecontrol-bin-2.6.1/projects/qpid-trunk/cpp/../python rpmbuild
--define "_topdir /usr/share/cruisecontrol-bin-2.6.1/projects/qpid-trunk/cpp/rpm"
--define "_sourcedir /usr/share/cruisecontrol-bin-2.6.1/projects/qpid-trunk/cpp" -ba
qpidc.spec error: line 9: Illegal char '-' in version: Version: incubating-M3
It's also not an increment from the previous 0.2 version number which is
liable to cause trouble with autoconf, rpmbuild or other version
sensitive tools.
Can I suggest we just go with 0.3? That's a nice normal version number
that is neatly aligned with M3, clearly suggests that we're a pre-1.0,
not-out-of-the-incubator yet release yet and definitely won't trip up
any packaging or version comparison tools.
I haven't made the change in case it needs discussion - we can probably
find some combo of characters that works if we absolutely must (maybe
0.3.incubatorM3 would work...) but I don't feel like farting around
testing all the things that might break if we can just use a normal,
sane numeric major.minor version like most of the software universe.
Cheers,
Alan.
We could also do 3.0 and have the Mx each be a major version number.
Incubator does not care that
we are pre 1.0 or not. 0.3 also works. depends on how we want to market
ourselves
Carl.
