Now 1.1 is out I'd like to bump this. I'd also like to ask how we handle package versioning for packages which need a tiny security/bug-fix during freeze or 1.1 lifetime when 1.2 is being worked on.
On 26/10/10 14:42, David Greaves wrote:
I think this is is one of my concerns; a changelog is supposed to tell me all I need to know about when changes were made. Currently they don't.
and
OK - is that a reasonable requirement though? Should a vendor be able to duplicate the OBS and be able to build MeeGo for, say, a slightly different architecture?
and
See above about dependencies and rebuilding. If we can't control -R and we use it to distinguish bug fixes/changes then different builds of MeeGo with the exact same rpm_X.Y.Z-R will have different bugs.
so
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.
ie X.Y.ZpRR No I don't think this is pretty but MeeGo is not SuSE and has additional requirements for the package version numbers. The other alternative is to use Release manually if the OBS can be setup to let us do this. On the "versioning packages in 2 branches" issue. The issue is potential version clashes: * X.Y.Zp2-2.1 is released in 1.1 * X.Y.Zp3-3.1 is released in 1.2 containing a feature patch then * X.Y.Zp4-4.1 is released in 1.2 containing the SVE patch and * X.Y.Zp3-3.1 is released in 1.1-security containing a SVE fix X.Y.Zp3-3.1 could now point to 2 different packages. So, just in the post release/freeze could we use: X.Y.Zr11p02 for packages changed in the old branch? Upgrades should of course work for all packages where X.Y.Z have changed but may require a touch for very stable packages where we have X.Y.Zr11p02 and, say, a X.Y.Zp04 Again, with access to -Release there may be a better answer. 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
