All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Mitchell <jumitche@redhat.com>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Steve Dickson <SteveD@RedHat.com>, linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/7] nfs-utils: Merge libnfsidmap tree with nfs-utils UPDATED
Date: Tue, 03 Oct 2017 09:15:07 +0100	[thread overview]
Message-ID: <1507018507.3567.8.camel@redhat.com> (raw)
In-Reply-To: <20171002163852.GC16092@parsley.fieldses.org>

On Mon, 2017-10-02 at 12:38 -0400, J. Bruce Fields wrote:
> On Mon, Oct 02, 2017 at 10:03:06AM -0400, Steve Dickson wrote:
> > 
> > 
> > On 09/14/2017 10:02 AM, Justin Mitchell wrote:
> > > It was suggested that merging the trees is more desirable than splitting
> > > the common code out into a shared library, so this patch set attempts to
> > > merge the libnfsidmap code into nfs-utils.
> > > 
> > > The main body of the code, copyright notices, and readme are copied
> > > across, omitting the shared conffile code, and trimming unused files
> > > like strlcpy.c and queue.h. The build files of both are adjusted to the
> > > new structure, and the dependent nfs-utils now link to the included
> > > shared library instead of an external one.
> > > 
> > > The source libnfsidmap tree did include some packaging files for
> > > debian/dkpg which have been omitted, there are no packaging materials in
> > > nfs-utils to merge them with, and i welcome advice on what should be
> > > done here.
> > > 
> > > Change: libnfsidmap imported as support/nfsidmap/ 
> > A quick status on this... I'm working on this but this patch is going
> > to cause a packaging nightmare... since the libnfsidmap package is 
> > required by nfs-utils which now is installing that lib... so
> > this might take some time... 
> 
> Would it help to start by keeping the separate libnfsidmap rpm, but just
> building it from nfs-utils instead of from separate source?

The BuildRequires for libnfsidmap is no longer necessary, as when you
configure and build nfs-utils from the top it will automatically build
and link to the merged libnfsidmap code.

I would expect then to list libnfsidmap as a sub-package within the
nfs-utils spec file so that the end result is the same set of rpms out
as we had before the merge.

Neither source tree contained any rpm packaging materials otherwise I
would have adjusted and tested it as part of the patch set.


  reply	other threads:[~2017-10-03  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 14:02 [PATCH 0/7] nfs-utils: Merge libnfsidmap tree with nfs-utils UPDATED Justin Mitchell
2017-09-14 14:03 ` [PATCH 1/7] nfs-utils: const-ify the config handling functions Justin Mitchell
2017-09-14 14:03 ` [PATCH 2/7] nfs-utils: Merge conf_get_str and conf_get_section Justin Mitchell
2017-09-14 14:04 ` [PATCH 3/7] nfs-utils: Add get_str with default value Justin Mitchell
2017-09-14 14:05 ` [PATCH 4/7] nfs-utils: split conffile to a separate convenience lib Justin Mitchell
2017-09-14 14:06 ` [PATCH 6/7] integrate libnfsidmap code with rest of nfs-utils Justin Mitchell
2017-09-14 14:07 ` [PATCH 7/7] nfs-utils: cleanup warnings from merged libnfsidmap code Justin Mitchell
2017-10-02 14:03 ` [PATCH 0/7] nfs-utils: Merge libnfsidmap tree with nfs-utils UPDATED Steve Dickson
2017-10-02 16:38   ` J. Bruce Fields
2017-10-03  8:15     ` Justin Mitchell [this message]
2017-10-30 14:49 ` Steve Dickson

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=1507018507.3567.8.camel@redhat.com \
    --to=jumitche@redhat.com \
    --cc=SteveD@RedHat.com \
    --cc=bfields@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    /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.