Jonathan Harris <jhar(a)tardis.ed.ac.uk> wrote:
This is a little ugly.
I agree. I'm not sure what else to do, though (although cynwin
users are probably quite happy using gunzip and tar).
If we're going to insist that the user has some
utilities installed, and we are, why insist on djtar instead of plain
gunzip and tar?
Well, mswindows is a bit brain-dead. In order to use something
like "gunzip | tar", one has to run some mswindows command processor.
Under Unix, one would have to invoke call-process with something like
"/bin/sh -c 'gunzip | tar'"; I'd have to construct something
ugly for mswindows. Also, under Win95/98 (I don't know about WinNT),
pipelines are run sequentially; e.g., gunzip is run and the results are
saved to a temporary file, and then tar is run with stdin coming from
the temporary file. For large .tar.gz files, this is unwieldly.
It's much nicer and faster to use a single-command solution; djtar,
being a single process, doesn't have to go through the "gunzip
completely before untarring" shenanigans. Because of this, djtar also
runs faster. Neither tar, gunzip, or djtar comes standard with
mswindows, and so I don't think it matters much which are used, as long
as they're easily obtained.
I've also been hacking on package-get some more: I've added a
function to display all packages, along with whether or not a package
has been installed, and whether or not it's obsolete (a newer version is
available). I'm probably going to mangle it some more to allow users to
select packages for installation/upgrading (vaguely like dired).
-- Darryl Okahata
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.