Re: New module for Fuse3

--000000000000176dd5064ea5def4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 4, 2026 at 6:50=E2=80=AFPM David Cantrell <[email protected]=
k> wrote:

> On 04/04/2026 17:33, Dominique Dumont via module-authors wrote:
>
> > Currently Fuse Perl module works with an old version of fuse C library.
> > Version 3 of libfuse was released in 2016.
> >
> > As a consequence, old C fuse library is deprecated and Fuse Perl module
> was
> > removed from Debian. (which breaks my Config::Model::FuseUI on Debian)
> >
> > So I've ported old Fuse module to fuse3.
> >
> > The interface changes are rather important, some functions are renamed,
> other
> > are removed, so I don't think trying to have a Fuse module working with
> old
> > fuse and fuse3 is a practical idea.
> >
> > So I've ported Fuse to fuse3 and plan to release it on CPAN. That said,
> I'm
> > not sure of the module name I should use.
> >
> > Can I use Fuse3 ?
> >
> > PS: I've cc'ed current Fuse maintainer
>
> There's nothing stopping you from calling it Fuse3, and there's
> precedent for the old version being at the top level. But consider
> whether it needs to be at the top level. There are a bunch of other
> modules under Filesys::* so I think that might be a good home for it.


Linux::* may also be a reasonable option.

Leon

--000000000000176dd5064ea5def4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Apr 4, 2026 at 6:50=E2=80=AFPM Da=
vid Cantrell &lt;<a href=3D"mailto:[email protected]">[email protected]=
g.uk</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">On 04/04/2026 17:33, Domin=
ique Dumont via module-authors wrote:<br>
<br>
&gt; Currently Fuse Perl module works with an old version of fuse C library=
.<br>
&gt; Version 3 of libfuse was released in 2016.<br>
&gt; <br>
&gt; As a consequence, old C fuse library is deprecated and Fuse Perl modul=
e was<br>
&gt; removed from Debian. (which breaks my Config::Model::FuseUI on Debian)=
<br>
&gt; <br>
&gt; So I&#39;ve ported old Fuse module to fuse3.<br>
&gt; <br>
&gt; The interface changes are rather important, some functions are renamed=
, other<br>
&gt; are removed, so I don&#39;t think trying to have a Fuse module working=
 with old<br>
&gt; fuse and fuse3 is a practical idea.<br>
&gt; <br>
&gt; So I&#39;ve ported Fuse to fuse3 and plan to release it on CPAN. That =
said, I&#39;m<br>
&gt; not sure of the module name I should use.<br>
&gt; <br>
&gt; Can I use Fuse3 ?<br>
&gt; <br>
&gt; PS: I&#39;ve cc&#39;ed current Fuse maintainer<br>
<br>
There&#39;s nothing stopping you from calling it Fuse3, and there&#39;s <br=
>
precedent for the old version being at the top level. But consider <br>
whether it needs to be at the top level. There are a bunch of other <br>
modules under Filesys::* so I think that might be a good home for it.</bloc=
kquote><div><br></div><div>Linux::* may also be a reasonable option.</div><=
div><br></div><div>Leon</div></div></div>

--000000000000176dd5064ea5def4--