PND package version number vs. application version number

[hmc]

Hi guys,


what version number is the one, which the Repo and PNDStore use to determine, if there is an upgrade available for a package? Is it the version number of the package, or the version number of the contained application(s)?


How should I handle versioning of a PND, which I build several PND packages for, each newer one is an improved version of the older one, but which contain the same application version number?


Should the package version number reflect the application version number, if the package contains only one application?


Or should the package version start at 1.0.0, no matter which application version is inside?


Thanks


Daniel

 

[sebt3]

The version is for the app that's in. Then, there is a build number for your work. that's the reason why the PND have 4 numbers : the last digit is the PND build number

 

[ivanovic]

The answer to your question is twofolded:


1) There is the version of the package. This is, together with the package id, what the repo and pndmanager(s) use to determin "this is more recent than that".


2) In theory a "package" can include various programs (applications). Eg you could ship a collection of various versions of Mupen64. So here it makes sense to make "real use" of the applications version which can differ from the package version. In most cases where you just have one application inside a package you want to make sure that both version numbers are just *IDENTICAL*.

 

[milkshake]

Its up to you how you version the package vs the version of the aplpication.


The version of the package is really just your package version, but that doesnt mean you cannot use the same version number as you did for your app you are free to make them match if you like.


But think about the following situations:


You may edit the package for some reason (add preview pics, fix run script or whatever) whithout increasing the actual app version.


You might have more than one app contained within the package so in that case the package version number cannot really reprisent the app version number as there are more than one app within the package.


but ultimately the choice is yours as long as it makes some sense, and as long as future updates to that package/app increase the number the repo will show its an update and so will any package managers.


hope that helps.