ubuntu-phone team mailing list archive

["Alejandro J. Cura" <alejandro.cura@xxxxxxxxxxxxx>]

On Mon, Mar 16, 2015 at 10:11 AM, Alejandro J. Cura
<alejandro.cura@xxxxxxxxxxxxx> wrote:
> On Sat, Mar 14, 2015 at 11:54 PM, Rodney Dawes
> <rodney.dawes@xxxxxxxxxxxxx> wrote:
>> On Fri, 2015-03-13 at 11:01 -0300, Alejandro J. Cura wrote:
>>> I agree with this point: when a click package has both a scope and an
>>> app, either the scope should take precedence or the devel should be
>>> able to choose how it's displayed in the store results (as an app or
>>> as a scope).
>>
>> It should display as both an app and a scope. The way it is now is due
>> to a limitation in the way packages with more than one app are handled.
>> Even if your package has multiple apps (which is possible), only the
>> first will appear in the store, and we only really handle a single app
>> in the package reasonably well in general. This needs some thought in
>> terms of implementation details, but I don't think it needs a bug with a
>> lot of discussion.
>
> I've seen this first with the "Untappd scope", so: No, it should not
> be shown automatically as both an app and a scope in the store. As
> pointed in this thread, developers consider the main focus of their
> package to be either an app or a scope.
>
> My proposal is to find some simple way to give the developer of a
> package some control over this option: whether to show the package in
> question in the store as a scope or as an app.
>
> For example, we could add a new optional field to the click manifest
> that points at the main click hook (eg: "main-hook: untappd"), and
> with a seemingly small change in the client and the server we could
> provide devels with control over this.
> This is the kind of small fix I think we should be discussing in a bug.

I've opened this bug: https://bugs.launchpad.net/bugs/1432636
If you are a scope devel affected by this, please mark the bug as
"affects me also".

cheers,
-- 
alecu