Support for looking in build-aux/snap

[Sergio Schvezov]

Look for snapcraft definitions in build-aux/snap as a preferred path over the snap directory for projects that have a snap directory for other purposes.

[Michael Vogt (mvo)]

We (the snapd team) would really like to have this feature. We have a "snap" directory that contains our (golang) code to deal with "snap" packages. So using snap/snapcraft.yaml is not practical for us.

[Sergio Schvezov (sergiusens)]

My proposal is to keep using .snapcraft.yaml to avoid yet another location for builders to find a valid definition, but allow a .snapcraft directory (could be empty) to indicate that that is the place to find assets like hooks, gui and others.

[Sergio Schvezov (sergiusens)]

We can leave the door open for a .snapcraft/snapcraft.yaml if need be in the future.

[Sergio Schvezov (sergiusens)]

After discussion in Malta we agreed to support build-aux/snap instead of .snapcraft as an alternative directory.

[Sergio Schvezov (sergiusens)]

https://github.com/snapcore/snapcraft/pull/2496

[Christopher Mcneill (krayziegamer7)]

Can't wait to see

[Launchpad QA Bot (lpqabot)]

Fixed in stable r18938 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18938>.