> Is solving this through documentation a better option?
IMHO, no. My point in filing this bug is that it's inconvenient for any special action to even be necessary.
snapcraft being a snap, I expect it to have its dependencies bundled, including the automated review tool.
If you don't want to do this, then feel free to Won't Fix it, but I would only consider this bug resolved if it's impossible to inadvertently build a snap that the public store will reject unless the user is promptly told that it'll be unacceptable for the store.
> We don't enforce it as the rules are different for each store.
That's something that IMHO you need to figure out. For example, default to behaving correctly for the public store, and allow configuration to relax the rules (or turn off the checker) to match a private store if the developer is targetting that.
> Is solving this through documentation a better option?
IMHO, no. My point in filing this bug is that it's inconvenient for any special action to even be necessary.
snapcraft being a snap, I expect it to have its dependencies bundled, including the automated review tool.
If you don't want to do this, then feel free to Won't Fix it, but I would only consider this bug resolved if it's impossible to inadvertently build a snap that the public store will reject unless the user is promptly told that it'll be unacceptable for the store.
> We don't enforce it as the rules are different for each store.
That's something that IMHO you need to figure out. For example, default to behaving correctly for the public store, and allow configuration to relax the rules (or turn off the checker) to match a private store if the developer is targetting that.