ti, 2010-10-26 kello 15:42 +0200, ext David Greaves kirjoitti: > On 26/10/10 13:38, Anas Nashif wrote: > > On 2010-10-26, at 1:01 PM, David Greaves wrote: > > You get the same version, but with different release.build number, because > > those are maintained in the MeeGo build system. > > And this is another. > What happens when a spec depends on >=X.Y.Z-R instead of >= X.Y.Z > (Which sounds reasonable given a bug is fixed in X.Y.Z-R)
A bit tougher case than just depends is upgradeability. Moving files between subpackages should be done by having conflicts with the previous versions. If there is X.Y.Z-1, the next version should have Conflicts: < X.Y.Z-2 (right?). Now if the release number gets bumped in between, upgrades will break. Or if the new package is rebuilt elsewhere and the release number gets reset to 1, it will become uninstallable. > Incidentally... I think a solution to this entire problem is as simple as > adding > an incrementing/resetting 'pXX' to the version number to specify the MeeGo > patchlevel; ie a manual supplement to -release. Do we have any real uses for the automatic -release? I would be happier to see that if release field exists in spec file it will override autoincrementation. I see absolutely no point in forcing specs to have it and then just ignore the content. -- Tapio Rantala _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
