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

--0000000000002b70a80572553292
Content-Type: text/plain; charset="UTF-8"

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.



--

In your time of need, may your piece be with you!

The trouble with many of today's college graduates is not that they're
ignorant, it's that they've been taught so much that just isn't so!

                                                      (with apologies to
Ronald Reagan).

--0000000000002b70a80572553292
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The port build mechanism built the RCS binaries and instal=
led the (by default, I suppose) in /usr/bin.=C2=A0 I built them to copy to =
a FreeNAS system which does not include RCS or the ability to build &quot;p=
orts&quot; (no tools).<div><br></div><div>For a couple reasons, I installed=
 those binaries in /usr/local/bin on the FreeNAS system.=C2=A0 Mostly they =
worked OK, but rcsdiff, for example, did not, emitting errors like: &quot;/=
usr/bin/co not found&quot;.=C2=A0 Examination of the rcsdiff binary reveale=
d a hard-coded path to /usr/bin/co which, obviously, will fail if the binar=
ies are installed in /usr/local/bin!=C2=A0 Apparently the co and ci binarie=
s also contain hard-coded paths for things in /usr/bin/ but did not seem to=
 use them in my tests.</div><div><br></div><div>RCS binaries on my other Li=
nux systems do not contain hard-coded paths and can be moved to any directo=
ry enumerated in the PATH env variable with no ill effect.</div><div><br></=
div><div><br></div><div><br clear=3D"all"><div><div class=3D"gmail_signatur=
e" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr=
"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><d=
iv dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D=
"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><di=
v><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div di=
r=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"=
><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div>
<div>
--<br><span><br>In your time of need, may your piece be with you!</span></d=
iv><div><span><br></span></div><div>The trouble with many of today&#39;s co=
llege graduates is not that they&#39;re</div><div> ignorant, it&#39;s that =
they&#39;ve been taught so much that just isn&#39;t so! <br></div><div><br>=
</div><div>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (with apologies to Ronald Reagan).<br></div>=
<div><br></div></div></div></div></div></div></div></div></div></div></div>=
</div></div></div></div></div></div></div></div></div></div></div></div></d=
iv></div></div></div></div></div></div></div></div></div></div></div></div>=
</div></div></div></div></div></div></div></div></div>
</div></div>

--0000000000002b70a80572553292--