Thanks for the reply (and link) !
I've examined Gabor Szabo' SCO
source:
MetaCPAN-SCO
his article:
Building an open source clone of search.cpan.org using the MetaCPAN API
which looks promising. But seems to require running a service on it's own port.
Which I'd like to avoid. While I guess I could (re)process metacpans data. That seems
grossly inefficient, and slow. especially given I'm already running a mirror.
Seems it'd be a whole lot smarter to simply pull the data from my own copy and process
that. Maybe populating a DB with it, and pulling it from there. This lead me to:
App::CPAN::Search
and
Package::Locator
but they're more Package centric, rather than: module | dist | author , as search, and
metacpan do
like:
CPAN::SQLite
but I don't think it'll scale well. But there's also:
CPAN::Search::Lite
which seems a bit closer, and might scale better, as well.
Anyway, that's as far as I've managed so far. But was hoping to I might find a quick
"drop in" replacement I might implement.
Thanks again!
¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|