🚀 go-pugleaf

I've tried to stay out of the lharc-zoo flamewars, but I need
this catharsis. I have been using lharc201i for a while and it
has always worked until today. Today I figured that I better
upgrade to lzh20ik, just to be on the safe side. Well, lo and
behold, my current lharc choked on some files, so I guess my
timing was right.

So what happens when I try to extract lzh201k? lharc201i chokes.
Now, we're not talking about lharc1.0 or something. There should
have been (at most) one minor revision between the two.

Do I really need 201j to unlzh 201k and is 201i too "out of date"?
IF this is the case, and my problem wasn't caused by cockpit error,
which is entirely possible, then I think that these lzh guys have
lost sight of the purpose of utilities in the first place. The
idea behind the lzh is to allow people to share files (compression
makes it easier to download files). It is a utility. I personally
don't care if the version I have will create subdomain crosslistings
and hierarchical bitbuckets :-) If -extract will work, I could live
with that. I can accept creating newer versions with more bells and
whistles as long as the basic functionality is preserved across all
versions. But this situation is ridiculous. I want to use lzh to
access files. I don't want to spend my time racing to keep up with
the latest version which is incompatible with anything that came
before.

People that upload .lzh files that they want the st community to
see should consider my reaction to a file that uses a newer version
of lzh and so I can't uncompress it - you know that trashcan on the
corner of the desktop? :-) My point is, if you want a lot of people
to access your software, you're better off putting it in a form people
can access.

And now my lharc flame:
	I have NEVER been unable to uncompress a file with zoo.

Mike Healy

healy@nosc.mil