On 25/10/10 15:32, Arjan van de Ven wrote:
On 10/25/2010 7: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
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.)"
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.
David
eh
OBS manages the release for you automatic so that it always increments
don't think we need to specify anything here ;)
Am I not right in thinking that this will be reset if, for example a package is
copied from 1 project to another?
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
