Aquileo | Recent changes to patches

Aquileo | #27 shell script to detect .7z encryption

2016-10-15T19:23:18.022000Z

Hope I solve buffering ambiguity soon and update the script accordingly.
About improving – seems the only way to really improve something is to switch to libarchive. But before we need to design a good abstraction layer above it.

Btw, who is Ettore? :-)

Aquileo | #27 shell script to detect .7z encryption

2016-10-15T18:25:37.100000Z

You're right, the same way as in xa_7zip_extract and sibling functions – construct command string and run command. What else may be expected?

Aquileo | #27 shell script to detect .7z encryption

2016-10-15T17:18:46.961000Z

/bin/sh detect_7z_encrypt.sh /path/to/detected/7z_binary /path/to/archive

exit code: 0 if encrypted, 10 (EXIT_CODE_NOT_ENCRYPTED) if not encrypted, else error (errors aren't expected though)

Note that script expects valid .7z archive file as second argument (I see no reason to detect is it .7z file or not because it is already done in your code. Am I right?)

There is some «optimisations» done – we are terminating 7z process after successful detection or after listing header is complete (MAX_READ_LINES). Or after READ_TIMEOUT seconds.

I've checked script running in bash sh mode and busybox sh. Hope it means enough compatibility level.

Also I've checked the earliest 7z version available for me (9.20), listing header format is same as 16.02, though file-roller code seems to expect another header format in addition. Maybe we should investigate it?

Right now I haven't implemented forced line-buffering yet, but it will be done soon.

Aquileo | shell script to detect .7z encryption

2016-10-14T15:57:23.360000Z

see DESCRIPTION inside script

Aquileo | #26 GTK+ 3 support

2014-12-24T11:28:01.708000Z

I'm not going to argue about proprietary and open source. I do not want to add another dependency Gyorgy, sorry.

I'm using your patch to have the SVN code use GTK+3 right now.

Your patches are welcome, thanks for your time :)

Aquileo | #26 GTK+ 3 support

2014-12-24T11:23:14.572000Z

You can use it also with the bsdtar binary. And the readme file is outdated, it supports writing 7z archives:
https://code.google.com/p/libarchive/issues/detail?id=41#c9

RAR is a proprietary format, and no open source tools are available to write into it, so I don't think it's so important.

I'm not really interested in a project that doesn't support libarchive/bsdtar.

Aquileo | #26 GTK+ 3 support

2014-12-24T09:13:28.524000Z

Because I would add another dependency. Also libarchive can't write RAR and 7Z:

rar (read only, starting in libarchive 3.0)
7-Zip (read only, starting in libarchive 3.0)

Did I convince you to concentrate your efforts on the faster and better SVN code?

Aquileo | #26 GTK+ 3 support

2014-12-24T02:21:50.199000Z

Why don't you just use libarchive as backend? It could able to read and write into many archive formats, so you don't have to deal with each command line extraction program.
http://libarchive.org/

Aquileo | #26 GTK+ 3 support

2014-12-23T20:42:57.914000Z

That's why is better to concentrate the efforts on one code. The one on the SVN can be ported to GTK+3 and forget about GTK+2 as it's undeveloped. This branch, 0.5.4 is buggy and slow. Try to open a 180MB zip file with both version. The SVN one open it instantly, the 0.5.4 freezes the GUI.

If you want I can port the SVN code o GTK+3 and get rid of all the deprecated API, in the meantime you could take care of completing the ZIP module by allowing it to allow add,test and dnd. Most of the code can be reused from this branch to do that. Look at the new extract dialog... does it sound tantalizing?

Aquileo | #26 GTK+ 3 support

2014-12-23T20:33:53.088000Z

Those deprecations are already there in the current code. I fixed all of them that affects the GTK+ 2 version. So if you build Xarchiver with '--disable-gtk3' configure flag, you won't see any of those messages. If you want to remove the rest of the deprecations introduced in GTK+ 3, then it breaks GTK+ 2 compatibility.

Note that all GTK+ based software uses deprecated API, because they changes the API every half a year. So you can't make your application compatible with multiple GTK+ versions and fix all deprecations at the same time, because the code would be unmaintainable due to many conditional code.