If anyone has been paying attention to my journal, you may have vaguely
heard about "pip" (which I named mostly because it's cute, easy to type
and not taken by anything other program in debian, but which we can also
call the "Perl Installer Program" if people like).
One feature I just added is URI support, so you can now use pip to take
a remote uri, uses a few tricks (i.e. CPAN::Inject) to inject it into
the CPAN client in a way that is identical to being pulled down from
CPAN itself, and then install it.
So I thought I'd pass on this testing tip.
Since I moved to SVN, one of the things I've been doing is commiting my
release tarballs into a /releases/ directory.
One side-effect of this is that even before I've uploaded it to CPAN,
ever release already has a URI.
For example, the new JSAN client I got half way through and then got
stalled on is currently at:
http://svn.phase-n.com/svn/cpan/releases/JSAN-Shell-2.00_04.tar.gz
So now you can do two things with the following command.
pip -i http://svn.phase-n.com/svn/cpan/releases/JSAN-Shell-2.00_04.tar.gz
Firstly, you can do an install of a tarball before you upload it that
behaves the same way with the CPAN client as if you had already uploaded it.
Second, if you upload a new module and want other people to test it
FAST, before the index is updated, but without your test people having
to download and install by hand, they can.
Just some tips I thought I'd pimp... ewr... I mean pass on.
Adam K
