From: Uwe Brauer <oub@mat.ucm.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
Subject: Re: rar 7z for dired-compress-file-suffixes and dired-compress-files-alist
Date: Tue, 12 Jun 2018 17:58:17 +0200 [thread overview]
Message-ID: <87d0wwvvxi.fsf@mat.ucm.es> (raw)
In-Reply-To: 83fu1sovsh.fsf@gnu.org
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> From: Uwe Brauer <oub@mat.ucm.es>
>> Date: Tue, 12 Jun 2018 17:09:36 +0200
>>
>> I have set these variables for me in order to support these formats
>> (provided that the relevant rar and 7z programs are installed)
>> accordingly and I could provide a patch. But I would like to know,
>> whether there are copyright issues, when adding these external programs.
> Yes, AFAIK the full-featured versions that run on Windows are not Free
> Software, and the Free variants are not capable of opening archives
> one finds nowadays.
> But I think you could use bsdtar (from libarchive) which is Free
> Software, at least for 7z. (I never tried, so I don't know how
> capable it is.)
I tested the free tools (on Ubuntu 16.06) which generated and extracted
rar abd 7z files. I did not test their compatibility with the latest
version on windows.
Bsdtar indeed openes these formats as well, but as far as I can see,
does not generate these formats.
So it seems, that given the difficulties concerning technical and
copyright issues, that these formats should not be added officially.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2018-06-12 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 15:09 rar 7z for dired-compress-file-suffixes and dired-compress-files-alist Uwe Brauer
2018-06-12 15:43 ` Eli Zaretskii
2018-06-12 15:58 ` Uwe Brauer [this message]
2018-06-12 16:05 ` Óscar Fuentes
2018-06-12 16:42 ` Eli Zaretskii
2018-06-12 17:03 ` Noam Postavsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0wwvvxi.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.