Hi,adding the VERSION files to the repo requires either one of those inconveniences:
1) Create a new branch for each "tagged" version that holds the version bump commit plus the version identifier files.
2) If you build from some source outside an official tagged versions, you might anyway get a package having the latest version number, as the files sit there.
3) Do not check in the version file at all but create source tarballs for each tagged version and serve them in parallel to the githib repo.
Option 3 would be the "idiot-proof" solution but requires a second infrastructure.
Oli -- Protect your environment - close windows and adopt a penguin!
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
