From: Steve Dickson <SteveD@redhat.com>
To: NeilBrown <neilb@suse.com>, Thorsten Kukuk <kukuk@suse.de>
Cc: linux-nfs@vger.kernel.org, libtirpc-devel@lists.sourceforge.net
Subject: Re: [Libtirpc-devel] [PATCH - rpcbind] Provide systemd unit files for rpcbind
Date: Mon, 7 Nov 2016 14:36:21 -0500 [thread overview]
Message-ID: <fb4dfafe-85ed-6f41-07a0-dd1e7714d6f8@RedHat.com> (raw)
In-Reply-To: <874m3pqun2.fsf@notabene.neil.brown.name>
On 11/02/2016 08:22 PM, NeilBrown wrote:
> On Thu, Nov 03 2016, Steve Dickson wrote:
>> Yes... basically
>>
>> -bin_PROGRAMS = rpcbind rpcinfo
>> +sbin_PROGRAMS = rpcbind rpcinfo
> Maybe
>
> -options like `--bindir=DIR' to specify different values for particular
> +options like `--sbindir=DIR' to specify different values for particular
>
> in INSTALL too??
I just left it alone... its been that way for years... Why fix something
that is not broken! ;-)
>> and that seems to work... all this means the rpm spec file
>> will have to be tweaked when a new release is made.
>>
>> All I'll for checking in these systemd file with the comments
>> from the systemd people and the bin=>sbin change.
>>
>> How about a respin?
> Attached
Thank you... Committed!
steved.
>
> Thanks,
> NeilBrown
>
prev parent reply other threads:[~2016-11-07 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 6:01 [PATCH - rpcbind] Provide systemd unit files for rpcbind NeilBrown
2016-11-01 16:51 ` Steve Dickson
2016-11-01 19:57 ` NeilBrown
2016-11-01 20:04 ` NeilBrown
2016-11-02 13:27 ` Steve Dickson
2016-11-02 13:49 ` [Libtirpc-devel] " Thorsten Kukuk
2016-11-02 18:06 ` Steve Dickson
2016-11-02 21:16 ` NeilBrown
2016-11-02 21:31 ` Steve Dickson
2016-11-03 0:22 ` NeilBrown
2016-11-07 19:36 ` Steve Dickson [this message]
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=fb4dfafe-85ed-6f41-07a0-dd1e7714d6f8@RedHat.com \
--to=steved@redhat.com \
--cc=kukuk@suse.de \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.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 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.