linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Eric Sandeen'" <sandeen@sandeen.net>
Cc: "'Hyunchul Lee'" <hyc.lee@gmail.com>,
	"'Sedat Dilek'" <sedat.dilek@gmail.com>,
	"'Goldwyn Rodrigues'" <rgoldwyn@suse.de>,
	"'LKML'" <linux-kernel@vger.kernel.org>,
	<linux-fsdevel@vger.kernel.org>
Subject: RE: [ANNOUNCE] exfatprogs-1.0.2 version released
Date: Fri, 24 Apr 2020 08:35:08 +0900	[thread overview]
Message-ID: <000001d619c7$d32434c0$796c9e40$@samsung.com> (raw)
In-Reply-To: <3f535421-d21b-0647-6e46-47b545ff3dfb@sandeen.net>

> 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
> >


  reply	other threads:[~2020-04-23 23:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200423084908epcas1p1b5d43c33b263b30844fc03a341f67413@epcas1p1.samsung.com>
2020-04-23  8:49 ` [ANNOUNCE] exfatprogs-1.0.2 version released Namjae Jeon
2020-04-23 13:43   ` Eric Sandeen
2020-04-23 23:35     ` Namjae Jeon [this message]
2020-04-23 14:44   ` 'Goldwyn Rodrigues'
2020-04-23 14:55     ` Eric Sandeen
2020-04-23 23:38     ` Namjae Jeon
2020-04-24  2:32       ` 'Goldwyn Rodrigues'

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001d619c7$d32434c0$796c9e40$@samsung.com' \
    --to=namjae.jeon@samsung.com \
    --cc=hyc.lee@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgoldwyn@suse.de \
    --cc=sandeen@sandeen.net \
    --cc=sedat.dilek@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).