So who would one talk to about improving CPAN's RSS feed of recent uploads?
It seems silly that at the very least the feed doesn't include the short descriptions visible on the recent upload page.
From there we could go on to a feed that included the full pod, pointers to the Changes and README files, the related modules info, etc...
We've got the metadata, lets use it.
Writing this journal entry probably took as long as writing a scraper would have, but hopefully it will lead to better things.
feed (Score:2)
I'm all for including the line from the SYNOPSIS.
But embedding the full pod seems a little unnecessary.
Were that I say, pancakes?
well... (Score:2)
I can't remember if I wrote that script or if graham did, though I suspect I did since it's readable and contains more than 10 lines :), but it hasn't changed much over the last few years...back when far fewer people bothered to put a synopsis in and search wasn't as good at extracting them. I don't know that the description would really be beneficial in an RSS feed since it's often long and just as vague and unenlightening as the name might be.
Re:well... (Score:1)
Re:well... (Score:2)
I didn't say it was either. The thing is that the 'synopsis' doesn't come with the distribution rather in the pod of each individual module contained in the distribution therefore making the attachment of the 'synopsis' to the distribution is a tricky and, at times, misleading task. It's a bit of a mismatch of information that works most of the time. Aside from that, I'd like to think that the brevity of the austere module listings in RSS is an encouragement to authors to name their modules well and descrip
an ETag perchance? (Score:1)
I don't know anything about the way search.cpan.org is implemented but it seems to me that somewhere there is code that has access to all the data we're talking about. I suspect this because the
But I take your word for it.
So I called it an early night (its too cold to get excited about being out late) and spent the last hour
Re:an ETag perchance? (Score:2)
the RSS code is not part of the shiny new rewrite, it's old and only got written because pudge pestered me about getting a newsfeed for the modules. Because the db is set up the way it is, this seemingly simple task isn't simple, which is why I pointed out that a distribution does not have 'metadata' that can be reliably used in this type of situation. People say we, cpan, should enforce such things or that perl6 will miraculously change this but my hope has waned. Just because it's perl6 doesn't mean it'll