On Sat, Oct 15, 2016 at 12:49 PM, Dan Kegel <d...@kegel.com> wrote:
I would like to hear yours instead :)
Take a look at  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 should we provide ways to overwrite and inject
values to all the fields? Maybe, I'm not sure. I think we should avoid to
make snapcraft a full templating engine. And for what I've seen, the
projects that need to change more than the version, or some more complex
replacing, they are already preprocessing some files before the build. In
that case, it could be reasonable to have a snapcraft.yaml.template in the
repository, and use sed, or the go text/template, or something like that to
generate the yaml before calling snapcraft.
We will have a session to design a solution for this during the sprint next
week. So please let us know your preference to take it into account.
¡paz y baile!
Snapcraft mailing list
Modify settings or unsubscribe at: