After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 502999 - Support for lzma
Support for lzma
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
: 507402 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-12-11 08:49 UTC by Sebastian Dröge (slomo)
Modified: 2008-01-05 08:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch implementing lzma support. (10.66 KB, patch)
2007-12-28 19:36 UTC, Ruben Vermeersch 		none Details | Review

Description Sebastian Dröge (slomo) 2007-12-11 08:49:57 UTC 
Hi,
it would be nice if file-roller could support lzma archives through lzma-utils.

http://tukaani.org/lzma/

Debian Bug: http://bugs.debian.org/455666
Comment 1 Ruben Vermeersch 2007-12-28 19:36:06 UTC 
Created attachment 101756 [details] [review]
Patch implementing lzma support.

Add support for lzma files, both normal files and tar-files compressed by lzma.
Fixes bug #502999.

 ChangeLog              |   11 +++++++++++
 src/fr-archive.c       |   18 ++++++++++++++++++
 src/fr-command-cfile.c |   24 ++++++++++++++++++++++++
 src/fr-command-tar.c   |   49 +++++++++++++++++++++++++++++++++++++++++++++++++
 src/main.c             |    4 ++++
 src/typedefs.h         |    3 +++
 6 files changed, 109 insertions(+)

This patch adds full support for lzma files. I have tested this on my basic use cases and it should perform without much trouble (as it is very similar to bzip2). I have not yet tested the nautilus extension, but this should not pose much problems.
Comment 2 Paolo Bacchilega 2007-12-30 09:41:51 UTC 
patch applied to trunk, thanks.
Comment 3 Paolo Bacchilega 2008-01-05 08:47:55 UTC 
*** Bug 507402 has been marked as a duplicate of this bug. ***