Re: Variables in snapcraft.yaml?

Hello there, thanks for your interest in improving snapcraft. El sábado, 15 de octubre de 2016 19h'46:35 ART, Dan Kegel escribió: I should think a simple general variable expansion in all string values would suffice for my use case. More complex use cases would be better

Re: Variables in snapcraft.yaml?

I should think a simple general variable expansion in all string values would suffice for my use case. More complex use cases would be better served by generating the .yaml file as I do now. So, yes, ${release-version}, but set it via --variable release-version=foo rather than

Re: Variables in snapcraft.yaml?

On Sat, Oct 15, 2016 at 12:49 PM, Dan Kegel wrote: > Thoughts? > I would like to hear yours instead :) Take a look at [1] where we started the discussion about setting the version in the yaml file. It seems that we should provide at least a way to overwrite the version; but

Variables in snapcraft.yaml?

I'm snapping an app that uses a library. The library has its major number in its package name and directories, as is customary. I'd like to use the same snapcraft.yaml even when the major number of the library changes (we build several versions all the time), except perhaps for changing a