We cannot keep the compatibility making it optional, unfortunately, because "run-snap snap.app args" is ambiguous with "run-snap snap.app cmd args". We cannot tell if the cmd there is part of the args or not. This would be a breaking change.
We might keep compatibility by introducing a second command that works in a different way, or by forcing a reboot and refreshing the launching scripts on update. On Tue, Mar 8, 2016 at 10:16 AM, Oliver Ries <oliver.r...@canonical.com> wrote: > On Mon, Mar 7, 2016 at 7:37 PM, Gustavo Niemeyer < > gustavo.nieme...@canonical.com> wrote: > >> Hello all, >> >> Today while sorting out some internal details of the on-going interfaces >> work with Zygmunt, the conversation and code review ended up reaching >> ubuntu-core-launcher and its parameters. >> >> The following document describes the issue, and presents two different >> proposals for how to address it. The primary is straightforward, and the >> secondary is better but takes more work. The recommendation is going with >> the primary now, and implement the secondary one once we have more time >> available. >> > > I am in favor of this recommendation, as it allows us to move to the > second approach when/if the underlying parts are done. It also allows us to > keep compatibility by making <command path> optional in v2 for a transition > period. > O. > -- gustavo @ http://niemeyer.net
-- snappy-devel mailing list snappy-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
