On Sat, Apr 4, 2026 at 6:50 PM David Cantrell <[email protected]> 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
