Hi Glenn,
thanks for your feedback.
Glenn Linderman schrieb:
Speaking as someone who thinks that PAR without pp would be totally
useless to me, I can still see that there could be some benefits in the
split. I have no problem with migrating stuff to use PAR::Packer's pp
instead of PAR's pp, as long as the functionality is still there.
There is no need to switch, until the PAR conversion is complete...
until a newer version of PAR + PAR::Packer becomes available, then using
the existing PAR (that includes a packer) is compatible. Once
everything works, one just installs both new modules, and everything
works, right? Or at least there would be a list of things that need to
be tweaked for the new/split version, and then things would work, right?
Right. It's really no more than a split of PAR+PAR::Heavy from the rest
of the distribution. PAR cannot depend on PAR::Packer or otherwise we
wouldn't have to do the split. But PAR::Packer would depend on PAR, so
you're alright if you just install PAR::Packer. In fact, as per Audrey's
suggestion, the svn version of pp now runs in the package "pp", so you
can actually do "install pp" from the CPAN shell and have it install
PAR::Packer. (When I make the next release, of course.)
The command line interface wouldn't need to change, just that pp is
suddenly supplied by a different module.
Exactly.
I'm not sure if there are any PAR APIs that would have to change, that
would be used within the packaged code... the unpackaging would simply
do all the necessary setup, and open the PAR archive, and the PAR APIs
would still be used, right?
Neither PAR nor PAR::Packer would change significantly code-wise.
Sounds like a pretty clean migration path, although, as you say, there
is a lot of work behind the scenes, and some significant documentation
changes, and a conceptual shift in thinking about what PAR is (and isn't).
Right again. It's the conceptual shift in thinking that is both part of
the reason and part of the problem.
Audrey said she thought this a good idea, so unless somebody objects,
I'll just do it in the development trunk when I find the spare time.
Cheers,
Steffen
