Comment 2 for bug 1662951

Thanks Gustavo -- makes sense.

I think from my point of view what I'm concerned about is that if I include a license.txt in the snap package definition (presumably in the `snap/` directory), it _will_ end up in the snap package, and this will happen automatically.

My interest here was sparked when I misinterpreted snapcraft deprecation notice 2 (introduced in snapcraft 2.26) and assumed that the license.txt file would also have to be moved from the `setup/` directory to the newly-required `snap/` directory (probably because I kept getting the deprecation message as long as the `setup/` dir existed).

However, I then noticed that the license.txt file seemed to be ending up in the snap package only by accident, as a consequence of the fact that the `snap/` directory winds up there (which is a bug). I'd like to make sure that the provided license.txt file still ends up in the snap package automatically, even when https://bugs.launchpad.net/snapcraft/+bug/1660890 is fixed.

As I recall, if I left `license.txt` in the old `setup/` directory, then it didn't get included in the snap package at all.

I understand if you want to push for the more general solution you outline above, and just require manual license-file solutions in the meantime, but just want to make sure that my main concern is understood.