license.txt and snap/ directory

[Kyle Fazzari]

On 02/06/2017 03:03 PM, Joseph Rushton Wakeling wrote:
> On 06/02/17 23:40, Sergio Schvezov wrote:
>> If it is not defined anywhere though, this is just a de-facto standard
>> as it really is upto each person creating there snap about where to
>> put it.
> 
> Well, that's what I'm saying -- IMO it should be defined (as I believe
> it used to be).
> 
>> Files owned by snapcraft will go in snap, files owned by snapd will go
>> in snapd. All the command wrappers that snapcraft creates will also go
>> in here.
> 
> Just to make sure I understand what you're saying, are you talking here
> about the directory layout of the snap package definition, or the
> generated snap package?
> 
> I'm talking about the directory layout in the generated snap package. 
> Currently an empty `snap/` directory gets created in there and I don't
> see the point of it if it does not contain anything.

The fact that an empty directory is created here is a bug[1]. It should
only create that directory if there's something to put in there. What
Sergio is saying is this:

Snapcraft-specific things, like hooks from snapcraft parts, command
wrappers (eventually, not yet) will end up in the snap/ directory of the
built snap. This has no bearing on the snap format, it's something
internal to snapcraft (it could just as easily have chosen to place
those things in the foo/ directory).

The things in meta/ are specific to snapd. This directory is literally
what defines "this random squashfs image" to be a snap.

[1]: https://bugs.launchpad.net/snapcraft/+bug/1660890

-- 
Kyle Fazzari (kyrofa)
Software Engineer
Canonical Ltd.
kyle at canonical.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170206/884671b2/attachment.sig>