From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 8968@debbugs.gnu.org
Subject: bug#8968: arc-mode 7z writing support
Date: Sat, 09 Jul 2011 19:34:59 +0800 [thread overview]
Message-ID: <878vs7n0v0.fsf@gnu.org> (raw)
In-Reply-To: <83iprcnf1z.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 09 Jul 2011 09:28:24 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I don't have a definitive answer. All I know is that arc-mode could
> not handle certain archives that I could handle with a 7z.exe
> downloaded for comparison. I then researched this issue and found out
> that those archives used a newer format that the Free Software
> variants of 7z did not support.
Were these archives .rar archives? If so, it is an older format, not a
newer one, and not the core format of 7z, just supported for
completeness. If not, then this is an issue that I cannot find any
information about - perhaps you could point us to the information so we
can stop recommending 7-Zip to others.
> on fencepost didn't support it. And the reason was that the newer
> formats used code that wasn't Free Software and whose sources were not
> available even under non-Free licenses.
Even the non-Free unRAR source is available, it just comes with
unacceptable restrictions on its use. So I'd be interested in what this
new format is.
next prev parent reply other threads:[~2011-07-09 11:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 21:47 bug#8968: arc-mode 7z writing support Juri Linkov
2011-07-01 2:55 ` Stefan Monnier
2011-07-04 22:22 ` Juri Linkov
2011-07-08 0:09 ` Juri Linkov
2011-07-08 7:08 ` Eli Zaretskii
2011-07-08 13:06 ` Stefan Monnier
2011-07-08 18:38 ` Juri Linkov
2011-07-08 19:49 ` Eli Zaretskii
2011-07-08 20:20 ` Juri Linkov
2011-07-09 6:28 ` Eli Zaretskii
2011-07-09 11:34 ` Jason Rumney [this message]
2011-07-09 13:05 ` Eli Zaretskii
2011-07-09 11:26 ` Jason Rumney
2011-07-08 15:56 ` Jason Rumney
2011-07-08 18:39 ` Juri Linkov
2011-07-08 19:51 ` Eli Zaretskii
2011-07-09 11:20 ` Jason Rumney
2011-07-09 22:27 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vs7n0v0.fsf@gnu.org \
--to=jasonr@gnu.org \
--cc=8968@debbugs.gnu.org \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).