Re: RCS binaries built on FreeBSD (the rcs "port")

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

() "Knight, Dave" <[email protected]>
() Tue, 31 Jul 2018 20:58:02 -0400

   The port build mechanism built the RCS binaries and installed
   the (by default, I suppose) in /usr/bin.  I built them to
   copy to a FreeNAS system which does not include RCS or the
   ability to build "ports" (no tools).

   For a couple reasons, I installed those binaries in
   /usr/local/bin on the FreeNAS system.  Mostly they worked OK,
   but rcsdiff, for example, did not, emitting errors like:
   "/usr/bin/co not found".  Examination of the rcsdiff binary
   revealed a hard-coded path to /usr/bin/co which, obviously,
   will fail if the binaries are installed in /usr/local/bin!
   Apparently the co and ci binaries also contain hard-coded
   paths for things in /usr/bin/ but did not seem to use them in
   my tests.

   RCS binaries on my other Linux systems do not contain
   hard-coded paths and can be moved to any directory enumerated
   in the PATH env variable with no ill effect.

Which version of RCS are you using?  The more recent versions
look for related programs in the same place where the invoked
program was found.

=2D-=20
Thien-Thi Nguyen

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iG4EARECAC4WIQR0jqDoHLinSJv6bORnAyIkTIB1AgUCX3tlzhAcdHRuQGdudXZv
bGEub3JnAAoJEGcDIiRMgHUC6EsAoKhEszT7GT9oEmhIm04aWWxDKFj1AKCed8tn
BTlFS5ZwXGB49Ej04vOSxA==
=Xz3c
-----END PGP SIGNATURE-----
--=-=-=--