Yuck, again answering to my own post.

Steffen Mueller wrote:
> I was wrong. At the very least, manual upgrading via
> $client->upgrade_module("Foo") works. After looking at it today, I added
> a bunch of new tests to the distribution. Seems to work fine so far.
> 
> I'm just about to make a new developer release 0.21_01 of
> PAR::Repository::Client with a whole load of bug fixes and new tests.

I have just uploaded another developer release of
PAR::Repository::Client: 0.21_02. It adds a manual setting for a
"cache_directory" so you can definitely keep the downloaded .par's
around. Furthermore, I just released a new stable version of
PAR::Repository (0.17) which fixes a caching-related checksum bug and
moves the whole range of improvements in the 0.16_* series to a stable
release.

This means that of the three caching strategies I mentioned earlier, two
are now implemented:

- The module/distribution indices are only checked for updates if the
checksum changed.
- If a distribution is to be downloaded, LWP::Simple::mirror is used, so
if the HTTP server supports if-modified since, nothing is downloaded
unless the distribution changed.
- All of this persists between runs since you can set cache_directory to
a non-temporary directory to bypass PAR's cleanup mechanisms.

Note that proxies might upset LWP::Simple::mirror. But there's little I
can do about that. Furthermore, the actual temporary directories used by
PAR when opening .par files on-demand are currently *not* persistent
between runs. If a lot of distributions are involved, that may also be a
bottleneck. *Maybe* in the future there will be more control over this.
But that becomes a PAR.pm issue and those are always more trouble than
the PAR::Repository::* ones because... I wrote the latter.

Cheers,
Steffen

Reply via email to