Date: Sat, 5 Apr 2014 12:19:17 -0700
From: "W. Trevor King" <wking@tremily.us>
To: Tomi Ollila <tomi.ollila@iki.fi>
Subject: Re: [PATCH 5/7] doc: Allow rst2man.py as an alternative to rst2man
Message-ID: <20140405191917.GF5316@odin.tremily.us>
References: <cover.1396718720.git.wking@tremily.us>
	<adce76bb9a0ca728d856da4ecaf6b282e22e7440.1396718720.git.wking@tremily.us>
	<m2a9bzd2bo.fsf@guru.guru-group.fi>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="hK8Uo4Yp55NZU70L"
Content-Disposition: inline
In-Reply-To: <m2a9bzd2bo.fsf@guru.guru-group.fi>
OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8;
	url=http://tremily.us/pubkey.txt
User-Agent: Mutt/1.5.22 (2013-10-16)
Cc: notmuch@notmuchmail.org
Precedence: list


--hK8Uo4Yp55NZU70L
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 05, 2014 at 10:05:31PM +0300, Tomi Ollila wrote:
> On Sat, Apr 05 2014, W. Trevor King wrote:
> > I use POSIX's 'command -v' [1] to find the path to rst2man=E2=80=A6
> >
> > [1]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/command.=
html
>=20
> =E2=80=A6
> Except the reference to _POSIX_ page. One knows how consistent these
> specifications are; alternative:
>=20
> http://pubs.opengroup.org/onlinepubs/009695399/utilities/command.html
>=20
> mentions additionally that -v flag
> "(On systems supporting the User Portability Utilities option.)"=20

It's been a decade since POSIX 2004 ;).  I'm not sure when the =E2=80=9CUser
Portability Utilities=E2=80=9D caveat was removed, but I imagine most
POSIX-aspiring shells have -v support.  Short of citing POSIX 2013, I
think I'd have to survey likely shells, and that seems even less
reliable.  Maybe I'm missunderstanding your suggested change?

> Also, we don't give such a treatment to other command either; I'd rather
> see RST2MAN=3Drst2man, RST2MAN=3Drst2man.py *and* RST2MAN=3D lines used
> instead -- the last to set RST2MAN to empty string instead of being unset.

I'm fine with that.  Alternatively, we could add an:

  if -n "${RST2MAN}"

clause to the front of the detection code to allow users with oddball
scripts (maybe a null set) to override RST2MAN at configure time:

  $ RST2MAN=3D/my/custom/rst_to_man_converter ./configure
  $ make

instead of at make-invocation time:

  $ ./configure
  $ make RST2MAN=3D/my/custom/rst_to_man_converter

That would consolidate configuration around the 'config' call, and
make explicitly emptying the RST2MAN variable more clearly superfluous
(although I'm still fine with an explicit empty).

Thoughts?

Trevor

--=20
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

--hK8Uo4Yp55NZU70L
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJTQFcyAAoJEKKfehoaNkbtS4cQAIJyV/E8CN6UswfjMPi251ja
crGZYM24x2cyVWC2bnfBLF0UwwQXoGKSRpVfnds0oMwrnP3pXZZDFT42t3hUXCoq
watxOmpUjzEC0CmGJdoM4RLzVbqZ7O7jxU+siEsOLkAn0jRiPQQMLBoz24UuEuTg
gNZbqfCdOBo+iiHp/JFdC002IrXOG1XGuULmsNfTechATG/LF+enA/ls8Jzo/Ats
Hk9+T+6ZvKqKrixeVUpWJcwaNdQsqUiRenX7tOGIZC0OQg+0SJmqoUdwYh8Gzpab
eOjC1kIh9bZ+LfGvmdjJs984epL0fue4UPk1K/XckX0WaPHKMn5OEqw1Lgm49PW1
lOsTUTDbZbmZd2MpvsQCUDRX5GKeZYn+3F4aRNx625IeythuohU2XZ84wpht7wm3
pu8JKVwjfdmhbCXX1B+fGWl6hVIOeD4oO+XkEUS2RD/uSD/dKUKJoYrhC+X9G+FJ
tzz1g9W6Tx6tmcympKqC7p9r714pIHwbZk05cCDdyUzupsPHvosndzt+/f/0kQnm
A3URoJjYq7DvGkGopNdMMRYKaUUtAyNjLPJ0wD4JYAOsGKKQagwInIlUXqIFjAVa
zb7htirrCRpkcw9Ormqn6RxJs8mf/J7C9XAIqDDQRWuBzB9dvBnVAHiGXd7mVXd8
Q/Kt6TaB/6B/M/ianv2f
=7TuE
-----END PGP SIGNATURE-----

--hK8Uo4Yp55NZU70L--