Dear Colleagues:
I now realize I should have figured out the answer to this question
earlier, but I did not.
I have a package (coot) whose most recent version is a pre-release.
As it fixes a lot of bugs, and I am in almost daily contact with the
author, we decided it was in good shape for fink.
The trouble is, the package is called coot_0.1.0-pre-1. When the non-
pre-release 0.1.0 comes out, I'm either going to have to convince him
to number it 0.1.1, or else figure out how to get around this:
dpkg --compare-versions 0.1.0-pre-1 gt 0.1.0 && echo "true"
true
In general, is there any way around this problem I accidently
created? (The only thing I could think of was calling it 0.1.0-pre-
N, where N is > the last pre-release number. That seems pretty ugly,
and won't match the tarball.)
Thanks.
Bill Scott
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
