Re: cpio-mode version 0.08

[Douglas Lewan <d.lewan2000@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]

On Tue, Jun 5, 2018 at 7:07 AM, Michael Albinus <michael.albinus@gmx.de>
wrote:

> Tom Tromey <tom@tromey.com> writes:
>
> Hi Tom,
>
> > It would be cool to have a cpio (and other archive type) file name
> > handler, so that dired could just be reused rather than reimplemented.
> > I realize this is possible with Tramp+GVFS now, but a pure elisp
> > implementation would be even better.
>
> ... and harder. Tramp uses GVFS only as transition layer, because it
> offers an API for libarchive(3). Switching to a direct access of the
> libarchive C API would have advantages:
>
> * Not bound to GVFS anymore, available on other platforms therefore.
> * Not bound to the restrictions GVFS has taken to libarchive, like no
>   support for writing into archives, missing proper file attributes, etc.
>
> I have been lazy so far, because Tramp knows already the GVFS API, and
> it was easy to add this support. But if there are heavy demands for
> change, I could consider to switch to libarchive.
>
> A pure Lisp implementation is wasted work, I believe. Look at the list
> of file formats libarchive supports. (info "(tramp) Archive file names")
>
> > Tom
>
> Best regards, Michael.
>

Indeed. I'd be more than happy to surrender to work to someone
who can provide a simpler implementation. I don't happen to know GVFS or
libarchive
or the question of how to bind lisp to a C library.

In the meantime, cpio-mode looks usable now for the archives it supports.
What remains is testing and polish. I would very much appreciate testing
from anyone who can help with it.

Thanks.

-- 
,Doug
Douglas Lewan
(908) 720-7908
Member of the PKRA.

[-- Attachment #2: Type: text/html, Size: 2624 bytes --]