On 01/25/2017 03:56 PM, Joseph Rushton Wakeling wrote: > Hello all, > > Quick question about version numbering (as in, the `version:` field of > `snapcraft.yaml`). The logical choice here is to use the version of the > app being packaged, but what's the recommended way to handle changes to > the snap package alone that don't change the version of the underlying app? > > Is a scheme like x.y.z-n advisable (where n is the revision number of > the snap itself for this version of the app), or are there alternative > suggestions? > > More generally, what are recommended practices for setting the > `version:` field of snap packages?
I personally use `version: <upstream version>snap1`. Then if I release an update that is snapping the same version of upstream but has snap-specific changes (wrappers, part changes, etc.) I can just release `<same version>snap2`. -- Kyle Fazzari (kyrofa) Software Engineer Canonical Ltd. [email protected]
signature.asc
Description: OpenPGP digital signature
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
