#269588 unshield: Version output and verify options

Package:
unshield
Source:
unshield
Description:
extracts CAB files from InstallShield installers
Submitter:
Markus Schaber
Date:
2023-12-13 13:03:04 UTC
Severity:
wishlist
#269588#5
Date:
2004-09-02 11:02:19 UTC
From:
To:
Hello,

I would like to send the following wishlist items to Santa Claus:

- Add a -v command line option/command that simply outputs the current
  version (and possibly a copyright notice).

- Add an option to verify the archive integrity (this could be
  implemented by extracting everything, but not actually saving the
  extracted data, as bzip2 does).

- Add an option to compare the archive contents with a bunch of
  extracted files (currently, I achieve this by extracting into a
  temporary directory and running diff over them).

What do you (or upstream) think about this Ideas?

Thanks for your patience,
Markus Schaber
#269588#10
Date:
2004-09-02 09:54:22 UTC
From:
To:
Hello,

Christmas is not that far away, so lets see :-)

regards
voc
#269588#15
Date:
2004-09-02 12:08:05 UTC
From:
To:
Sounds reasonable. (Even though I may use -V and allow -v for a future
"verbose" option.)

Also reasonable.

I'm reluctant to implement this. Could you provide a good use-case
scenario?
#269588#20
Date:
2004-09-02 17:16:07 UTC
From:
To:
Hello, David,
Hello, Volker,

Thats better, you're right.

I can follow this, so let me explain the situation I needed such a
feature:

From time to time, we get bunches of GIS Data from NavTeq (about 28 Gig
unpacked, distributed using about 45 half-filled CDs). As we develop
using linux, we don't use the crappy Windows installer and a human slave
to unpack the data, but simply copy all CDs to a big Harddisk and then
run a 5-line shell script using unshield to unpack the data.

Now, some weeks later we found that some (about half a douzen) of the
11thousand unpacked files had some corrupt data, and we were interested
whether this was due to some bit flipping during unpacking due to some
hardware problem or when copying around between our machines, or due to
having corrupted files included into the archive at NavTeq, and so we
needed a simple way to verify the unpacked archives.

I know this is an uncommon situation, and I'm not upset if you don't
implement it.

Thanks for your patience,
Markus Schaber
#269588#25
Date:
2004-09-12 14:35:21 UTC
From:
To:
Hi,

Now I understand why you wanted the comparison function. Maybe it will
be possible to see the MD5 sums for the files in the future, that could
simplify a shell script for the comparison.

However, I only implemented the first two wishes of yours. The changes
should be available in anonymous CVS within 24 hours.