On 2 September 2016 at 15:01, Stuart Bishop <[email protected]> wrote:
> > > On 2 September 2016 at 00:46, Leo Arias <[email protected]> wrote: > >> This is a pain point for me too. Most upstreams store the version number >> in only one place, because editing more than one for every tagged >> release is too boring. >> > > This is what https://bugs.launchpad.net/snapcraft/+bug/1594794 is about. > > The plugin can extract a version number in many cases (and plugins could > be added that just do this - eg. pull the version from debian/changelog or > git tags | grep release | naturalsort | tail -1 or run staging/usr/bin/foo > --version or whatever). So a particular part might know its version, and we > could declare which part's version is used for the snap. No need to specify > anything on the command line, and it would work with Launchpad without > extra work. > (Or if that is too complicated, just a command that is run at the end of staging or at the start of priming to generate the version number) -- Stuart Bishop <[email protected]>
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
