Hey all,
Day 3 of using snapcraft, and I've managed to get
both piglit and a proprietary app snapped and running.
Snapcraft's learning curve is not too steep, kudos.
Problem: I can't do 'snapcraft cleanbuild' on my proprietary
apps because they depend on packages in a ppa and/or a
private apt repo
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 variable
I probably just annoyed everyone with this email, but I thought I would follow
up with it and say that the issue is resolved. The user figured it out. He
reinstalled snapd after his upgrade of Ubuntu, then reinstalled the rubecube
snap, and then it worked. So that's good to know. I would hav
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 should we provide wa
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 --release-version=
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 served by generating
