On 2010-10-25, at 10:31 AM, David Greaves wrote: > On 25/10/10 15:00, Anas Nashif wrote: >> >> On 2010-10-25, at 9:40 AM, David Greaves wrote: >> >>> http://wiki.meego.com/Packaging/Guidelines >>> >>> An upstream package may have a fixed x.y.z and we can't use the -release >>> extension for packaging only changes. >>> >>> Under Version, it already says: >>> >>> Post-release packages: Packages released after a "final" version. These >>> packages contain the same numeric version as the "final" version, but have >>> an additional non-numeric identifier. >>> >>> For clarity I've added "This mechanism may also be used for packaging only >>> changes to an upstream package". >>> >>> Comments? >> >> I am not sure I understand this. Can you give an example? > > If you can see: https://projects.maemo.org/bugzilla/show_bug.cgi?id=200067#c8
I can't. > > quote:"To be exact, it's 0.61.25-1.1 and the fix is in 0.61.25-2.1. (As in, > same > upstream version, newer packaging.)" > What is the upstream version? You are referring to a packaging version in some other build system and want to reference that in meego? IMO that does not make sense, since the packaging is meego specific and any other previous packaging versioning and release really do not apply for meego. It is like saying we take a package from fedora and follow their packaging releases and versions.. > If the packaging changes then the proper package version should be > incremented - right? And since the source is not modified and the -release > can't be used then a non-numeric should be appended. > Packaging version 0 starts in meego, and not somewhere else. We cant adopt versioning history of packages from other systems into meego. Anas > David > > > -- > "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
