I ran into a problem at a customer's yesterday when I found that
openssh no longer prepends the OpenPKG bin directory to the PATH
on the server. Looking back through my archives, this appears to
have happened between Release 2.1 and Release 2.2. This causes
things like ``rsync -e ssh xxx'' to fail on the remote system or
to find invalid configuration if there's a vendor supplied
version of the program on the remote end that conflicts with the
OpenPKG version of the program.
The attached patch fixes this in what I think is a logical manner
for OpenPKG Release 2.2, 2.3, and CURRENT.
Bill
--
INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/
``The Income Tax has made more Liars out of American people than Golf has.''
Will Rogers
--- openssh.spec.orig 2005-02-21 09:02:29.000000000 -0800
+++ openssh.spec 2005-03-28 18:59:46.000000000 -0800
@@ -42,7 +42,7 @@
Group: Security
License: BSD
Version: %{V_base}%{V_portable}
-Release: 2.3.0
+Release: 20050328
# package options
%option with_fsl yes
@@ -218,8 +218,8 @@
--without-rsh \
--with-mantype=man \
--disable-etc-default-login \
- --with-default-path=/bin:/usr/bin \
- --with-superuser-path=/bin:/usr/bin:/sbin:/usr/sbin \
+ --with-default-path=%{l_prefix}/bin:/bin:/usr/bin \
+
--with-superuser-path=%{l_prefix}/bin:%{l_prefix}/sbin:/bin:/usr/bin:/sbin:/usr/sbin
\
--with-privsep-user=%{l_nusr} \
--with-privsep-path=%{l_prefix}/var/openssh/empty
