From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] add configure option --with-root-libdir
Date: Mon, 27 Aug 2018 19:56:19 -0400 [thread overview]
Message-ID: <20180827235619.GA2304@thunk.org> (raw)
In-Reply-To: <20180827165744.GB74162@jaegeuk-macbookpro.roam.corp.google.com>
On Mon, Aug 27, 2018 at 09:57:44AM -0700, Jaegeuk Kim wrote:
>
> Thanks. I've added this and been testing with other patches for next release.
>
Are you planning on doing a new release soon?
I'm also wondering if you could give some color commentary on how
often you plan on bumping the shared version library numbers? The
reason why I ask is because there is a Debian package which depends on
libf2fs and libf2fs-format, android-libf2fs-utils. It appears to be
part of the Android SDK.
I was about to send the Debian maintainer of android-libf2fs-utils
package a ping asking him or her to relink against the latest so
versions --- libf2fs.so.5 and libf2fs-format.so.4. But if the next
release is going to involve a bump of the so versions again, I'll hold
off requesting a rebuild of the package.
And if the shared libraries are going to be regularly bumped due to
incompatible ABI changes, should I recommend the andorid-f2fs-utils to
statically link instead of link against the f2fs shared libraries?
(I haven't bumped the e2fsprogs so versions in over a decade, but
that's because I had carefully designed the interfaces to allow for
backwards compatibility as we added new features to the file system.
I didn't know if that was part of your plan for f2fs-tools)
Thanks!!
- Ted
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-08-27 23:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 3:04 [PATCH 1/2] add configure option --with-root-libdir Theodore Ts'o
2018-08-20 3:04 ` [PATCH 2/2] Ask git to ignore the generated sg_write_buffer executable Theodore Ts'o
2018-08-20 7:21 ` Chao Yu
2018-08-27 15:51 ` [PATCH 1/2] add configure option --with-root-libdir Theodore Y. Ts'o
2018-08-27 16:57 ` Jaegeuk Kim
2018-08-27 23:56 ` Theodore Y. Ts'o [this message]
2018-08-28 7:12 ` Jaegeuk Kim
2018-08-28 14:25 ` Theodore Y. Ts'o
2018-08-28 16:59 ` Jaegeuk Kim
2018-08-29 3:10 ` [PATCH 1/2] add cotnfigure " Theodore Y. Ts'o
2018-08-29 21:04 ` Jaegeuk Kim
2018-08-29 23:51 ` Theodore Y. Ts'o
2018-08-28 3:43 ` [PATCH 1/2] add configure " Chao Yu
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=20180827235619.GA2304@thunk.org \
--to=tytso@mit.edu \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.