On Feb 03, 2017, at 10:06 AM, Steve Langasek wrote: >AIUI ubuntu-image will never consume these fields anyway, they're only for >snapd's use. Is it better to future-proof ubuntu-image by making it >maximally permissive on these fields? snapd parses the gadget.yaml before >it ever returns it to ubuntu-image, so it's not as if ubuntu-image being >strict helps us fail early.
That could be reasonable for the u-i implementation, if the contents of the defaults: section will never be relevant for u-i. If it's possible u-i will have to someday act on those contents, then I think it should be stricter, under the principle that it's easier to relax constraints than tighten them. Either way, the spec should still be more explicit about what's accepted. Cheers, -Barry
pgpa7nvHoYPCi.pgp
Description: OpenPGP digital signature
-- Devices mailing list [email protected] Modify settings or unsubscribe at: https://lists.snapcraft.io/mailman/listinfo/devices
