unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: "Trent W. Buck" <trentbuck@gmail.com>
Cc: stefan@marxist.se, 52477@debbugs.gnu.org
Subject: bug#52477: 27.1; .crx and .crx3 are zip files
Date: Fri, 24 Dec 2021 14:51:30 +0100	[thread overview]
Message-ID: <875yrecdr1.fsf@gmx.de> (raw)
In-Reply-To: <YcP0kNVEH8KqWoxs@hera.lan> (Trent W. Buck's message of "Thu, 23 Dec 2021 15:01:20 +1100")

"Trent W. Buck" <trentbuck@gmail.com> writes:

Hi Trent,

> It seems to me that:
>
>   1. when given a file in pyz/crx/crx format,
>      libarchive will auto-detect and use zip format.
>
>      I think it just finds the zip archive at an offset, and
>      leaves content before that offset alone.
>
>      This would allow it to read/extract/edit existing pyz/crx/crx3,
>      but not create a new one.
>
>      This is also true for libarchive bsdtar and Info-ZIP unzip,
>      although the latter emits a warning about the offset.
>
>   2. when given a file in pyz/crx/crx format,
>      emacs arc-mode will not auto-detect zip format.
>
>   3. when given a file in pyz/crx/crx3 format,
>      file-roller & nautilus will not auto-detect any format.

Well, I don't know how in detail nautilus/file-roller have integrated
libarchive. I believe they use the GVFS mount backend which calls
libarchive, but I don't know it for sure. So we agree that a native
libarchive integration in Emacs is preferred.

Best regards, Michael.





  reply	other threads:[~2021-12-24 13:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14  4:56 bug#52477: 27.1; .crx and .crx3 are zip files Trent W. Buck
2021-12-15 20:51 ` Stefan Kangas
2021-12-16  8:56   ` Michael Albinus
2021-12-16  9:22     ` Eli Zaretskii
2021-12-16 11:59       ` Michael Albinus
2021-12-16 13:21         ` Eli Zaretskii
2021-12-19 13:09           ` Lars Ingebrigtsen
2021-12-22  3:50           ` Trent W. Buck
2021-12-22 12:20             ` Michael Albinus
2021-12-23  4:01               ` Trent W. Buck
2021-12-24 13:51                 ` Michael Albinus [this message]
2021-12-22 12:55             ` Eli Zaretskii

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=875yrecdr1.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=52477@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    --cc=trentbuck@gmail.com \
    /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).