Dtrx

-----------

New features
~~~~~~~~~~~~

* Add support for RAR archives. Thanks to Peter Kelemen for the patch.

Bug fixes
~~~~~~~~~

* Previous versions of dtrx would fail to extract certain archive types
with the ``-v`` option specified. This has been fixed.

* dtrx 6.3 no longer imports the sets module unless it's running under a
very old version of Python, to avoid deprecation warnings under Python
2.6.

-----------

New features
~~~~~~~~~~~~

* --one-entry option: Normally, if an archive only contains one file or
directory with a name that doesn't match the archive's, dtrx will ask
you how to handle it. With this option, you can specify ahead of time
what should happen.

Bug fixes
~~~~~~~~~

* Since version 6.0, when you extracted or listed the contents of a cpio
archive, dtrx would display a warning that simply said "1234 blocks."
dtrx 6.2 suppresses this message.

* When you try to list the contents of an archive, dtrx will now cope with
misnamed files more gracefully, giving more accurate results and showing
fewer error messages.

* dtrx 6.2 will only show you error messages from archive extraction if it
is completely unable to extract the file. If one of its extraction
methods succeeds, it will no longer show you the error messages from
previous extraction attempts.

* dtrx is now better about cleaning up partially extracted archives when
it encounters an error or signal.

* Users will no longer see error messages about broken pipes from dtrx.

-----------

New features
~~~~~~~~~~~~

* Add support for InstallShield archives, using the unshield command.

* The wording of many of the interactive prompts has been adjusted,
hopefully to be clearer and provide more information to the user
immediately.

Bug fixes
~~~~~~~~~

* dtrx 6.1 does a better job protecting against race conditions when
extracting a single file.

* If you used the -f option, and extracted an archive that only contained
one file or directory, dtrx 6.0 would still prompt you to ask how it
should be extracted. dtrx 6.1 fixes this, extracting the contents to
the current directory as -f requires.

* Recursive extraction would not work well in dtrx 6.0 when the contents
of the original archive were a single file. This has been fixed in dtrx
6.1.

-----------

New features
~~~~~~~~~~~~

* When you specify -v at the command line, dtrx will display the files it
extracts, much like tar.

* When dtrx prompts you about how to handle recursive archives, you now
have the option of listing what those archives before making a decision.

* dtrx will now provide more information about why a particular extraction
attempt failed. It will show you error messages from all the attempts
it made, rather than only the last error it got. It will also detect
and warn you when one of the underlying extraction tools, like
cabextract, cannot be found.

* dtrx does a better job of cleaning up after itself. It wouldn't always
clean up temporary files after certain errors; that has been fixed. It
also catches SIGINT and SIGTERM and cleans up before finishing
execution.

Bug fixes
~~~~~~~~~

* Version 5.0 introduced a regression such that dtrx would not offer to
extract recursive archives that were hidden under subdirectories.
Version 6.0 fixes that.

* dtrx would not properly extract recursive archives when the original
archive contained a single directory. This has been fixed.

-----------

Bug fixes
~~~~~~~~~

* Version 5.0 did not work with Python 2.3; it used a new language
feature. This release fixes that.

-----------

New features
~~~~~~~~~~~~

* dtrx can now extract Ruby gems, 7z archives, and Microsoft Cabinet
archives. It can also handle files compressed with lzma, and extract
the metadata from Debian packages and Ruby gems.

* dtrx will now use several strategies to try to figure out what kind of
file you have, and extract it accordingly. If one doesn't work, it'll
try something else if it can.

* dtrx now displays more helpful errors when things go wrong.

* Previous versions of dtrx would look at what files were included in an
archive, and then make a decision about how to extract it. Now, it
always extracts files to a temporary directory, and figures out what to
do with that directory afterward. This should be slightly faster and
nicer to the system.