From: NeilBrown <neilb@suse.com>
To: Steve Dickson <SteveD@redhat.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: Thu, 03 Nov 2016 11:22:57 +1100 [thread overview]
Message-ID: <874m3pqun2.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <bf20e38d-6129-688f-42b8-aad97334daea@RedHat.com>
[-- Attachment #1.1: Type: text/plain, Size: 620 bytes --]
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??
>
> 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
Thanks,
NeilBrown
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Provide-systemd-unit-files-for-rpcbind.patch --]
[-- Type: text/x-patch, Size: 0 bytes --]
next prev parent reply other threads:[~2016-11-03 0:23 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 [this message]
2016-11-07 19:36 ` 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=874m3pqun2.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=SteveD@redhat.com \
--cc=kukuk@suse.de \
--cc=libtirpc-devel@lists.sourceforge.net \
--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 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).