Someone needs to take jwz aside...
diment at gmail.com
Fri Jun 10 10:33:38 BST 2011
I believe that metacpan will be open source. I think the correct answer regarding search.cpan is:
a. insufficiently generic problem space and/or problems solved in a hurry
b. which leads to the accumulation of cruft.
c. b continues to interact with c.
On 10/06/2011, at 7:12 PM, Paul Makepeace wrote:
> (Sorry, let's try that with the correct attribution - the reply was to
> James wherein metacpan.org reminded me about search.cpan.org not being
> On Fri, Jun 10, 2011 at 10:10, Paul Makepeace <paulm at paulm.com> wrote:
>> On Fri, Jun 10, 2011 at 09:10, On 8 Jun 2011, at 15:57, Matt Sergeant wrote:
>>>> I'm actually liking it more than CPAN for publishing and installing stuff. The only weak area is lack of search.cpan.org.
>> Why is search.cpan.org code (still) not open source?
More information about the london.pm