Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Corentin Chary <iksaif@g.o>
Subject: Re: Re: RFC: Add new remote-id types in metadata.dtd
Date: Fri, 18 May 2012 08:46:18 +0200
On Thu, May 17, 2012 at 2:02 AM, Kent Fredric <kentfredric@...> wrote:
> On 13 May 2012 07:43, Torsten Veller <tove@g.o> wrote:
>> * Corentin Chary <corentin.chary@...>:
>>> On Sat, Apr 21, 2012 at 03:33:18PM +1200, Kent Fredric wrote:
>>> >                                     { "term": { "status":"latest"} },
>>> >                                     { "term": { "module.authorized":"true"}}
>>
>> What does this mean?
>> - "latest"? this term looks like maintenance work.
>> - what is "authorized"?
>
> "latest" means that it will fetch metadata for whatever is deemed the
> most recent non-dev release, which is really the only sane option to
> go for if you want a list of modules that currently pertain to the
> distribution.  You could request *all* releases and then find a union
> of elements ... but that would be both erroneous and very time
> consuming.
>
>> It doesn't even list "Moose" for Moose?
>
> Its probably falling outside the initial 10 results, I forgot it did that,
>
>> 02packages.details.txt.gz lists 72 package names for Moose-2.0602.
>>
>
> Need to bolt on a { "size": 100 }  to the query to expand how may
> results it will return.

Updated remotesid.py to use that, correctly add Moose in the diff now !

>  curl -XPOST 'http://api.metacpan.org/module/_search' -d '
> {
>       "fields": [
>               "module.name",
>               "release"
>       ],
>       "query": {
>               "constant_score": {
>                       "filter" : {
>                               "and" : [
>                                       { "term": { "distribution":"Moose" } },
>                                       { "term": { "status":"latest"} },
>                                       { "term": {
> "mime":"text/x-script.perl-module"}},
>                                       { "term": { "indexed":"true"}},
>                                       { "term": { "module.authorized":"true"}}
>                               ]
>
>                       }
>               }
>       },
>       "size": 100
> }
>
> ^  that | grep module.name  | wc -l   # 83
>
> --
> Kent
>
> perl -e  "print substr( \"edrgmaM  SPA NOcomil.ic\\@tfrken\", \$_ * 3,
> 3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"
>
> http://kent-fredric.fox.geek.nz
>
Replies:
remote-id cpan-module
-- Torsten Veller
References:
Re: RFC: Add new remote-id types in metadata.dtd
-- Kent Fredric
Re: RFC: Add new remote-id types in metadata.dtd
-- Corentin Chary
Re: RFC: Add new remote-id types in metadata.dtd
-- Kent Fredric
Re: RFC: Add new remote-id types in metadata.dtd
-- Corentin Chary
Re: RFC: Add new remote-id types in metadata.dtd
-- Kent Fredric
Re: RFC: Add new remote-id types in metadata.dtd
-- Corentin Chary
Re: RFC: Add new remote-id types in metadata.dtd
-- Kent Fredric
Re: RFC: Add new remote-id types in metadata.dtd
-- Corentin Chary
Re: RFC: Add new remote-id types in metadata.dtd
-- Kent Fredric
Re: RFC: Add new remote-id types in metadata.dtd
-- Corentin Chary
Re: RFC: Add new remote-id types in metadata.dtd
-- Torsten Veller
Re: Re: RFC: Add new remote-id types in metadata.dtd
-- Kent Fredric
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: RFC: Add new remote-id types in metadata.dtd
Next by thread:
remote-id cpan-module
Previous by date:
Re: news item: Portage's config-protect-if-modified feature is enabled by default
Next by date:
Re: news item: Portage's config-protect-if-modified feature is enabled by default


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.