Looking for pointers how to set up lzma stream using xz-devel

Bruno Wolff III bruno at wolff.to
Mon Jan 4 18:18:11 UTC 2010


On Mon, Jan 04, 2010 at 07:57:54 -0600,
  Jon Ciesla <limb at jcomserv.net> wrote:
> I've actually come across this WRT UPX as well.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=501636
> 
> From what I can tell. . .we may be stuck unless someone wants to
> write some docs.

I am going to get squashfs-tools working with lzma eventually. I am just hoping
it would be easier rather than harder.

Note that waiting for the "lzma" library isn't going to work. We need to either
package the SDK or switch to using xz. The "lzma" library is no longer being
developed upstream. (And is based on a version of the SDK that is too old
to be easily used in squashfs-tools.)

It looks like using xz will be a bit work setting up an equivalent wrapper
for squashfs-tools, but will avoid packaging a third version of lzma in
Fedora. The main issue for me is understanding what needs to be done. The
amount of code needed should be under 100 lines.

If other things in Fedora also need something need more lzma support, then it's
probably worth figuring out if we can use the same solution.

It seemed odd that the debian bug for this claimed that source from the SDK
was needed. Presumably an appropriate library would work. It may be that
lzma-devel here is different from what debian has. I didn't look at it too
carefully after seeing it was based on an old and incompatible version of the
SDK that I need for squashfs-tools and that upstream switched to xz.

I suspect that packaging the SDK without the extra lmza utils wouldn't be
too bad. We can probably drop those now that xz is packaged. I haven't looked
at this carefully though.




More information about the fedora-devel-list mailing list