Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Alias (5735)

Alias
  (email not shown publicly)
http://ali.as/

Journal of Alias (5735)

Tuesday January 02, 2007
09:39 PM

Tool Day: New releases of pler and pip

[ #32055 ]

A collection of releases finishes up my New Year tools refreshing.

* The complete collection of PITA::Test::Dummy modules were updated to remove the spurious QA test that added a dep.

* A new CPAN::Test::Dummy::Perl5::Developer module was added, which guarentees never to be in the index. (useful for a variety of interesting small things).

* CPAN::Inject has been updated to use the same configuration semantics as CPAN itself, so that it now injects to the right place in sudo scenarios.

* pler now works and has been tested on all three of Mac, Linux and Win32.

In bigger news, I managed to complete the refactoring of the internals of pip to be primarily URI-based.

As well as being generalised better now, it also means you can describe packages to install as arbitrary URIs, and they will be downloaded, injected into the local CPAN cache and installed, with full recursive CPAN deps followed.

Which also means now pip can provide a convenient one liner for installing a tarball from any URI.

So now you can install modules straight out my repository, with no messy download/extract/make/install cycle. 100% Ashton's Law compliant! :)

    sudo -H pip --install http://svn.phase-n.com/svn/cpan/releases/Process-0.17.tar.gz

It also means that if you have a p5i file somewhere containing file names, it will work both from the local system and via relative URIs.

Which also means you can now script an installation that mixes and matches tarballs from various servers, and still does the right thing when installing their CPAN dependencies.

pip is now at the point where I have uses for it on a weekly, if not bi-daily basis.

Next up (when I have some time) is allowing the use of both module names and dist paths in p5i files.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.