There is an
alternative search engine to CPAN
for which a CPAN-weekly mailing list has been setup.
We are beta-testing it right now.
You can email the maintainer of the website and beta-test
along with us!
Alternatively, here is a "perl" script which you can put
in your cron and get a weekly text/plain
email of cpan.org/RECENT.html.
I quoted Perl above because I am leveraging both mail and
lynx and external technologies instead of writing a Pure
perl script.
#!/usr/bin/perl
$ENV{TERM}='vt100';
$recent_file='/tmp/RECENT.txt';
$email_file='/tmp/ARRIVALS.txt';
$email_recipient_list='princepawn@yahoo.com';
system "lynx -dump http://www.cpan.org/RECENT.html > $recent_file";
open T, $recent_file;
while (<T>) {
/(authors.*readme$)/ && push @readme, $1;
}
`echo "" > $email_file`;
for $readme (sort @readme) {
my $url = "http://www.cpan.org/$readme";
warn $url;
system "lynx -dump $url > X";
system "echo $url >>$email_file";
system "head -5 X >>$email_file";
system "echo >>$email_file; echo >>$email_file";
}
`cat $email_file | mail $email_recipient_list`;
-
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.
|