Le mardi, 4 mars 2003, à 15:34 Europe/Paris, Max Horn a écrit :
At 9:01 Uhr -0500 04.03.2003, Benjamin Reed wrote:Max Horn wrote:E.g. take the example of 5.0-RC1 followed by 5.0. What do you propse should be done here to make it debian version compliant? 4.99999 and 5.0 ? or 5.0 and 5.0a ? Or what? None of them seems appealing to me. Both can potentially conflict with actual version of the package (e.g. they might really release a 5.0a some times after to fix something).
What I normally do is munge the release, which is the "least significant bit".
So I would make it 5.0-0rc1.1
If I had to make another release, it's 5.0-0rc1.2
Then when final comes out, it becomes 5.0-1.
That sounds like a senseible approach to me.
me too
In any case, no matter what we decide, we should formalize it and make it part of the packaging docs.
indeed, if we want people to follow this.
-- zauc
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
