> -----Original Message-----
> From: Chris Wareham [mailto:chris.wareham@iosystems.co.uk] 
> Sent: 29 July 2004 15:25
> To: Gary Parker
> Cc: port-sparc@NetBSD.org
> Subject: Re: Newbie pkgsrc PATH Related Question
> 
> 
> One method is to modify the PATH in /etc/profile (for Bourne type
> shells). I don't user C shell, but I guess that modifying 
> /etc/csh.login
> would work for that shell. For /etc/profile, set the PATH to something
> like:
> 
>   PATH=/usr/pkg/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
>   export PATH
> 
> This doesn't help if users override the default PATH in their 
> own shell
> config files though. In that case you can get pkgsrc to 
> install over the
> top of the "system" binaries. I've never needed to do this 
> myself, but a
> quick perusal of Packages.txt in your pkgsrc directory may provide the
> answer.

Well thanks for the speedy response Chris.

My problem isn't really with 'user' binaries, as it were...I understand how
to change my PATH so that as I user I can access the binaries I've compiled
and installed in /usr/pkg, it's more the daemons and libraries that the
system itself loads that I'm struggling with.

The exact issue I'm having is with OpenSSL: the system obviously comes with
a base install of openssl to enable sshd to function. However, as I'm sure
you know being an SS5 user, openssl compiled with a V7 target is slower than
a 3-legged dog in treacle so I've compiled openssl from pkgsrc and done a
'make install' but everything gets installed into the /usr/pkg tree and the
system prefers to use the files in /usr and /usr/lib.

How do I get my system to use the optimised openssl binaries I've compiled
instead of the base install ones?

Gary