At least it seems to be fast :-)
On Wed, Oct 2, 2013 at 5:30 PM, Alejandro J. Cura < alejandro.c...@canonical.com> wrote: > On Fri, Sep 27, 2013 at 6:05 PM, Martin Albisetti > <martin.albise...@canonical.com> wrote: > > On Fri, Sep 27, 2013 at 5:17 PM, Ricardo Kirkner > >> Also, for proper filtering I suppose the full architecture list is to be > >> sent to the click index, right? So that we can have queries per specific > >> arch, disregarding of the filename (ie, even if the name contains 'all' > or > >> 'multi', the click index would know the package supports armhf and > amd64, > >> for example) > > > > Yes, absolutely sent to click index. > > I'm making a click-scope branch to send the architecture as part of > the search query. > > I first tried getting the architecture via uname, but I can only get > the linux arch (armv7l on my nexus 4, x86_64 on my desktop) > > The right way seems to be with "dpkg --print-architecture", which > returns armhf and amd64 as expected. > Any objections to the scope using that? > > cheers, > -- > alecu > > -- > 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 >
-- 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
