Top-level package names, UX questions

[Gustavo Niemeyer]

On Mon, Mar 16, 2015 at 4:57 PM, Mark Shuttleworth <mark at ubuntu.com> wrote:
>
> The question is:
>
>  * do I now have to refer to commands in that package as
> foo.beuno.command, or
>  * can I just say foo.command (I prefer this)
>
> but that means that
>
>  * if there is an "official" foo, I must choose between beuno's foo and
> that one
>  * because foo.command :)
>
> I think the latter choice is reasonable to have to make.
>

Indeed, and it would probably be reasonable to happen as well on any other
ambiguity besides the official aliases (foo.beuno and foo.sabdfl, say).

This reminds me of Android's intent system, where a given intent is handed
off automatically if there's only one subscriber to the given intent, but
every time an application is installed that could also receive the given
intent, the user again has to choose which application should handle it,
and whether the choice should be pinned for future cases.

That system is significantly more flexible, though, as the choice is per
action, rather than per package.

Ideally, nothing changes at all on disk (except perhaps in a database
> somewhere).


+1


gustavo @ http://niemeyer.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20150316/5061a658/attachment.html>