What is the benefit of deviating from conventional package versioning?
Wes On Sep 29, 2009, at 2:49 PM, Michael March wrote: > > My only complaint with the current numbering scheme is that at a > glance it looks like the webpy team is implying the webpy is WAY off > from being a 1.0 release. > > Personally, I mostly understand the rationale behind it but the few > times I have sold using webpy internally for corporate projects it has > caused me to have to do some needless extra explanation. > >> Quoting "Anand Chitipothu" <[email protected]>: >>> Aaron's idea was to use a floating point number for version and most >>> systems don't interpret version that way. >>> Debian package uses version as 0.210, 0.320 etc for backward- >>> compatibility. >>> >>> Can you please let me know what is troubling you? >> >> It means, that the Debian packages always have to have a different >> numbering scheme than upstream. Currently, Debian uses a trick called >> "epoch", but this is not meant to be incremented with every new >> release. >> dpkg does not understand the floating point numbering scheme :~( >> >> What about RPM? Does it work better in that respect? >> >> Would you consider counting from 0.32 up from now on? That would make >> the life of Debian/Ubuntu packagers easier. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
