Snapcraft as post-build operation?
Adam
aps337 at gmail.com
Tue Jun 7 19:30:22 UTC 2016
Hi All,
Pretty excited about the concept of snaps. I have an application I
want to port over, but I'm a little confused about where to start.
Seems like part of the concept is to integrate the build machinery for
a project and make it a "slave" to Snapcraft. Unfortunately the
application I want to port over, a database backed web server based
application has some pretty complex build machinery that's evolved
over many years.
I can't help but think that it makes more sense, for my application at
least, to think of Snapcraft like an application installer build that
happens post-build. None of the examples seem to fit that model
though.
Am I trying to put a square peg in a round hole? If what I am doing
seems feasible, where do I start? Can I setup the yaml file to just cp
files over from my output directory and then build up the contents of
my snap that way?
Thanks for any insight and help you can provide.
More information about the Snapcraft
mailing list