Package: wnpp
Version: N/A
Severity: wishlist
* Package name: exfatprogs
Version: 1.0.4
Upstream Author: namjaejeon
* URL : https://github.com/exfatprogs/exfatprogs
* License : GPL-2.0 License
Description: exfat utilities for the kernel's version of the exfat
filesystem driver.
"exfatprogs
As new exfat filesystem is merged into linux-5.7 kernel, exfatprogs is
created as an official userspace utilities that contain all of the
standard utilities for creating and fixing and debugging exfat
filesystem in linux system. The goal of exfatprogs is to provide high
performance and quality at the level of exfat utilities in windows. And
this software is licensed under the GNU General Public License Version 2.
"
Long description taken from its github page.
This is the official exfat utilities meant to support the kernel's
implementation of the exfat driver.
Note there are 3 exfat drivers, this one being the only one meant to be
used directly within the kernel giving the best performance of all 3.
Since this exfat driver performance is better than the others, it would
be a good idea to request that support for the reverse-engineered exfat
implementation no longer be adequate.
^ Debian should drop support for the package exfat-utils, and instead
rely on Kernel 5.7 (for its available built-in exfat driver support),
and have exfatprogs to maintain and work with the exfat-linux driver.
^ The mistake I see happening is untested and possible
incompatibilities(and/or issues) going with "exfat-utils" along with the
native exfat-linux driver.
Instead it should be only "exfatprogs" with "exfat-linux".
It would imho make more sense to package this by the time kernel 5.7
becomes packaged into debian, as by then users would be getting confused
which exfat driver they should be using.
Some sources online mention that Kernel 5.7 is favorable to start using
with the exfatprogs utilities.
https://lore.kernel.org/lkml/001201d60e12$8454abb0$8cfe0310$@samsung.com/
"The initial version(1.0.1) of exfat-utils is now available.
This is the official userspace utilities for exfat filesystem of
linux-kernel."
^ Also keep in mind, that namjaejeon, had the project renamed to
"exfatprogs" --- likely due to the already named package "exfat-utils"
in debian.
so https://github.com/exfat-utils/exfat-utils now redirects to
https://github.com/exfatprogs/exfatprogs
Important note: afaict, the exfat-utils and exfatprogs have no relevance
to one another. This can be seen by reading discussions about
announcements on their bugtracker on github between these two projects,
neither one are merging and it appears that these two projects will
remain separate.
The confusion for me finding out about this, is that the URL/project
page has been renamed, as even the story about the new "exfatprogs"
announcement on the phoronix site also uses the prior confusing name.
https://www.phoronix.com/scan.php?page=news_item&px=Samsung-exFAT-Utils-Release
"
Samsung Releases exFAT-Utils To Format File-System, Fsck
With the new exFAT file-system merged for Linux 5.7, Samsung engineers
responsible for this open-source native Linux kernel driver for
Microsoft's exFAT file-system support have now issued their first
official release of exfat-utils.
The exfat-utils 1.0.1 release out this morning is their first official
release of these user-space utilities for exFAT on Linux. The
exFAT-utils package allows creating an exFAT file-system with mkfs.exfat
as well as adjusting the cluster size and setting a volume label. There
is also fsck.exfat for consistency checking of an exFAT file-system on
Linux.
"
The github link entitled with the name "exfat-utils" provide on phoronix
now also redirects to exfatprogs -- should there be a renewed editorial
on both LKML and phoronix, they should instead be edited and re-titled
with the project name "exfatprogs".
So the confusion I hope regarding the naming could be set aside, even
though the official announcement and other reports about it uses the
obsolete naming for it.... but afaict it has nothing to do with
"relan's" exfat project which is stored at a separate location somewhere
on github.
