Eric Blake wrote:
The upstream maintainer used the version number 3.00-0.02, which doesn't play very nicely with setup.exe, so I named the package bashdb3 at version 0.02.
Potential problem:If bash increments its version number, and bashdb then resets its suffixed version number when it moves to the new bash version, your scheme will break.
e.g.: 3.00-0.02 => bashdb3-0.02 3.01-0.01 => ?????I'd suggest using bashdb-3.00_0.02, to avoid this - i.e. change hyphen to underscore.
Max.
