On Fri, Jun 27, 2014 at 4:36 PM, Ted Gould <t...@ubuntu.com> wrote: > > Currently we're putting the UI component of the Payments service into the > Click Store. This shouldn't be something that a user installs, sees in a > search or could possibly purchase. It is useful to have go through the same > update mechanisms of have the other Click machinery associated with the > store. What we've discussed is having a way for the Click store to identify > "system components" much like it does scopes and applications so that it can > filter them for the search. > > What I'm proposing for this is that we add a stanza as a "hook" that we > don't actually implement on the client anywhere today. The hook name would > be "system-component" and it would point to a JSON file that today, for this > example would just have "type" and "pay-ui". This would allow us to add > other metadata as needed in the future. > > Thoughts?
Given I urged you to go down this path, I don't want to now oppose the plan (although it *is* tempting!). The only thing I think I would mention is that we should be careful to not end up re-inventing apt and dependencies. That's just a general hand-wavy statement, but something to keep in mind and maybe take us back to the drawing board if these types of cases come up too often. -- Martin -- Mailing list: https://launchpad.net/~ubuntu-appstore-developers Post to : ubuntu-appstore-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-appstore-developers More help : https://help.launchpad.net/ListHelp
