[ANNOUNCE] exfatprogs-1.0.2 version released

[ANNOUNCE] exfatprogs-1.0.2 version released

[Namjae Jeon]

This is the second release of exfatprogs since the initial version(1.0.1).
We have received various feedbacks and patches since the previous release
and applied them in this release. Thanks for feedback and patches!

According to Goldwyn's comments, We renamed the project name from
exfat-utils to exfatprogs. However, There is an opinion that just renaming
the name is not enough. Because the binary names(mkfs.exfat, fsck.exfat)
still are same with ones in current exfat-utils RPM package.

If that's real problem, We are considering a long jump with 2.0.0 when adding
repair feature.

Any feedback is welcome!:)

The major changes in this release:
 * Rename project name to exfatprogs.
 * label.exfat: Add support for label.exfat to set/get exfat volume label.
 * Replace iconv library by standard C functions mbstowcs() and wcrtomb().
 * Fix the build warnings/errors and add warning options.
 * Fix several bugs(memory leak, wrong endian conversion, zero out beyond end of file) and cleanup codes
 * Fix issues on big endian system and on 32bit system.
 * Add support for Android build system.

The git tree is at:
      https://github.com/exfatprogs/exfatprogs

The tarballs can be found at:
      https://github.com/exfatprogs/exfatprogs/releases/tag/1.0.2

Re: [ANNOUNCE] exfatprogs-1.0.2 version released

[Eric Sandeen]

On 4/23/20 3:49 AM, Namjae Jeon wrote:
> This is the second release of exfatprogs since the initial version(1.0.1).
> We have received various feedbacks and patches since the previous release
> and applied them in this release. Thanks for feedback and patches!
> 
> According to Goldwyn's comments, We renamed the project name from
> exfat-utils to exfatprogs. However, There is an opinion that just renaming
> the name is not enough. Because the binary names(mkfs.exfat, fsck.exfat)
> still are same with ones in current exfat-utils RPM package.
> 
> If that's real problem, We are considering a long jump with 2.0.0 when adding
> repair feature.
> 
> Any feedback is welcome!:)

Just my $0.02 - I think you need to keep the binary names the same, this is a
very common naming convention that other software may depend on.  At least
xfstests certainly expects that the "exfat.$FOO" naming convention is there,
and that "exfat" is used consistently across utilities, module names, statfs
and blkid output etc.

Personally I think it would be sufficient for distribution packages to set the
equivalent of a "Conflicts: exfat-utils" in the exfatprogs package so that they
cannot be installed simultaneously?  The devil is in the details on packaging
but there are usually packaging tricks if we need to replace or exclude one
package with another.

Thanks,
-Eric

> The major changes in this release:
>  * Rename project name to exfatprogs.
>  * label.exfat: Add support for label.exfat to set/get exfat volume label.
>  * Replace iconv library by standard C functions mbstowcs() and wcrtomb().
>  * Fix the build warnings/errors and add warning options.
>  * Fix several bugs(memory leak, wrong endian conversion, zero out beyond end of file) and cleanup codes
>  * Fix issues on big endian system and on 32bit system.
>  * Add support for Android build system.
> 
> The git tree is at:
>       https://github.com/exfatprogs/exfatprogs
> 
> The tarballs can be found at:
>       https://github.com/exfatprogs/exfatprogs/releases/tag/1.0.2
> 

RE: [ANNOUNCE] exfatprogs-1.0.2 version released

[Namjae Jeon]

> On 4/23/20 3:49 AM, Namjae Jeon wrote:
> > This is the second release of exfatprogs since the initial version(1.0.1).
> > We have received various feedbacks and patches since the previous
> > release and applied them in this release. Thanks for feedback and patches!
> >
> > According to Goldwyn's comments, We renamed the project name from
> > exfat-utils to exfatprogs. However, There is an opinion that just
> > renaming the name is not enough. Because the binary names(mkfs.exfat,
> > fsck.exfat) still are same with ones in current exfat-utils RPM package.
> >
> > If that's real problem, We are considering a long jump with 2.0.0 when
> > adding repair feature.
> >
> > Any feedback is welcome!:)
> 
> Just my $0.02 - I think you need to keep the binary names the same, this is a very common naming
> convention that other software may depend on.  At least xfstests certainly expects that the
> "exfat.$FOO" naming convention is there, and that "exfat" is used consistently across utilities,
> module names, statfs and blkid output etc.
Okay, I will keep them.
And he is saying that the version of mkfs/fsck.exfat in exfatprogs should be higher than
the version 1.3.1 of mkfs/fsck.exfat in current exfat-utils package to reduce the confusion of
old users. For this reason, it confuses me whether it makes sense to significantly increase the version.
So I'm thinking about raising the version to 2.0.0 when the big feature like repair comes in.
> 
> Personally I think it would be sufficient for distribution packages to set the equivalent of a
> "Conflicts: exfat-utils" in the exfatprogs package so that they cannot be installed simultaneously?
> The devil is in the details on packaging but there are usually packaging tricks if we need to replace
> or exclude one package with another.
Oh, there's a way.
Thanks for your opinion!
> 
> Thanks,
> -Eric
> 
> > The major changes in this release:
> >  * Rename project name to exfatprogs.
> >  * label.exfat: Add support for label.exfat to set/get exfat volume label.
> >  * Replace iconv library by standard C functions mbstowcs() and wcrtomb().
> >  * Fix the build warnings/errors and add warning options.
> >  * Fix several bugs(memory leak, wrong endian conversion, zero out
> > beyond end of file) and cleanup codes
> >  * Fix issues on big endian system and on 32bit system.
> >  * Add support for Android build system.
> >
> > The git tree is at:
> >
> > https://protect2.fireeye.com/url?k=f7b9f8ba-aa6aa104-f7b873f5-0cc47a31
> > ba82-14a9f1852cdf3dd6&q=1&u=https%3A%2F%2Fgithub.com%2Fexfatprogs%2Fex
> > fatprogs
> >
> > The tarballs can be found at:
> >
> > https://protect2.fireeye.com/url?k=35b018cd-68634173-35b19382-0cc47a31
> > ba82-7c9ab2990d663462&q=1&u=https%3A%2F%2Fgithub.com%2Fexfatprogs%2Fex
> > fatprogs%2Freleases%2Ftag%2F1.0.2
> >

Re: [ANNOUNCE] exfatprogs-1.0.2 version released

['Goldwyn Rodrigues']

Hi Namjae,

On 17:49 23/04, Namjae Jeon wrote:
> This is the second release of exfatprogs since the initial version(1.0.1).
> We have received various feedbacks and patches since the previous release
> and applied them in this release. Thanks for feedback and patches!
> 
> According to Goldwyn's comments, We renamed the project name from
> exfat-utils to exfatprogs. However, There is an opinion that just renaming
> the name is not enough. Because the binary names(mkfs.exfat, fsck.exfat)
> still are same with ones in current exfat-utils RPM package.
> 
> If that's real problem, We are considering a long jump with 2.0.0 when adding
> repair feature.
> 
> Any feedback is welcome!:)

I agree with Eric. We can add "Conflicts" flag to make sure there are
conflicting capabilities in packages.

> 
> The major changes in this release:
>  * Rename project name to exfatprogs.
>  * label.exfat: Add support for label.exfat to set/get exfat volume label.
>  * Replace iconv library by standard C functions mbstowcs() and wcrtomb().
>  * Fix the build warnings/errors and add warning options.
>  * Fix several bugs(memory leak, wrong endian conversion, zero out beyond end of file) and cleanup codes
>  * Fix issues on big endian system and on 32bit system.
>  * Add support for Android build system.
> 
> The git tree is at:
>       https://github.com/exfatprogs/exfatprogs
> 
> The tarballs can be found at:
>       https://github.com/exfatprogs/exfatprogs/releases/tag/1.0.2
> 

Can we follow the standard of source tarballs be
<projectname>-<version>.tar.gz? In this case, exfat-1.0.2.tar.gz
instead of 1.0.2.tar.gz?

-- 
Goldwyn

Re: [ANNOUNCE] exfatprogs-1.0.2 version released

[Eric Sandeen]

On 4/23/20 9:44 AM, 'Goldwyn Rodrigues' wrote:
> Hi Namjae,

...

>> The git tree is at:
>>       https://github.com/exfatprogs/exfatprogs
>>
>> The tarballs can be found at:
>>       https://github.com/exfatprogs/exfatprogs/releases/tag/1.0.2
>>
> 
> Can we follow the standard of source tarballs be
> <projectname>-<version>.tar.gz? In this case, exfat-1.0.2.tar.gz
> instead of 1.0.2.tar.gz?

better yet exfatprogs-1.0.2.tar.gz :)

Thanks,
-Eric

RE: [ANNOUNCE] exfatprogs-1.0.2 version released

[Namjae Jeon]

> Hi Namjae,
Hi Goldwyn,
> 
> On 17:49 23/04, Namjae Jeon wrote:
> > This is the second release of exfatprogs since the initial version(1.0.1).
> > We have received various feedbacks and patches since the previous
> > release and applied them in this release. Thanks for feedback and patches!
> >
> > According to Goldwyn's comments, We renamed the project name from
> > exfat-utils to exfatprogs. However, There is an opinion that just
> > renaming the name is not enough. Because the binary names(mkfs.exfat,
> > fsck.exfat) still are same with ones in current exfat-utils RPM package.
> >
> > If that's real problem, We are considering a long jump with 2.0.0 when
> > adding repair feature.
> >
> > Any feedback is welcome!:)
> 
> I agree with Eric. We can add "Conflicts" flag to make sure there are conflicting capabilities in
> packages.
Okay.
> 
> >
> > The major changes in this release:
> >  * Rename project name to exfatprogs.
> >  * label.exfat: Add support for label.exfat to set/get exfat volume label.
> >  * Replace iconv library by standard C functions mbstowcs() and wcrtomb().
> >  * Fix the build warnings/errors and add warning options.
> >  * Fix several bugs(memory leak, wrong endian conversion, zero out
> > beyond end of file) and cleanup codes
> >  * Fix issues on big endian system and on 32bit system.
> >  * Add support for Android build system.
> >
> > The git tree is at:
> >
> > https://protect2.fireeye.com/url?k=c2ec59b9-9f266c0e-c2edd2f6-0cc47a30
> > 03e8-e469846ab6add112&q=1&u=https%3A%2F%2Fgithub.com%2Fexfatprogs%2Fex
> > fatprogs
> >
> > The tarballs can be found at:
> >
> > https://protect2.fireeye.com/url?k=88473660-d58d03d7-8846bd2f-0cc47a30
> > 03e8-7bb3906eafbb32bc&q=1&u=https%3A%2F%2Fgithub.com%2Fexfatprogs%2Fex
> > fatprogs%2Freleases%2Ftag%2F1.0.2
> >
> 
> Can we follow the standard of source tarballs be <projectname>-<version>.tar.gz? In this case, exfat-
> 1.0.2.tar.gz instead of 1.0.2.tar.gz?
Ah, When I tried to download it through this link, source tarballs was exfatprogs-1.0.2.tar.gz...
Am I missing something ?
> 
> --
> Goldwyn

Re: [ANNOUNCE] exfatprogs-1.0.2 version released

['Goldwyn Rodrigues']

Hi Namjae,

On  8:38 24/04, Namjae Jeon wrote:

<snip>

> > >
> > > The tarballs can be found at:
> > >
> > > https://protect2.fireeye.com/url?k=88473660-d58d03d7-8846bd2f-0cc47a30
> > > 03e8-7bb3906eafbb32bc&q=1&u=https%3A%2F%2Fgithub.com%2Fexfatprogs%2Fex
> > > fatprogs%2Freleases%2Ftag%2F1.0.2
> > >
> > 
> > Can we follow the standard of source tarballs be <projectname>-<version>.tar.gz? In this case, exfat-
> > 1.0.2.tar.gz instead of 1.0.2.tar.gz?
> Ah, When I tried to download it through this link, source tarballs was exfatprogs-1.0.2.tar.gz...
> Am I missing something ?

The filename on the link is:
https://github.com/exfatprogs/exfatprogs/archive/1.0.2.tar.gz

When I extract it, it extracts to exfatprogs-1.0.2 though.

-- 
Goldwyn