> Well I think pkgsrc is wonderful.   I have some questions and
> some problems with packages to report.
> 
> 1) How can I setup my system so that /usr/pkg/bin and
> /usr/pkg/sbin are always in my PATH.4, and specifically before
> /usr/local/bin?  I know this is pretty basic.  I appologize.

You can put it in your $HOME/.profile, or $HOME/.kshrc if you have it setup.

If you want it global, you can modify /etc/profile. Or, in your /etc/rc.d/rc.local, you can set the CS_PATH

setconf CS_PATH $(getconf CS_PATH):/usr/pkg/bin

> 2) How can I setup my system so that /usr/pkg/lib is always
> checked for the pkgsrc libraries?  When compiling a pkgsrc package this
> seems to happen automatically, but what if I'm compiling
> my own programs?

This is explained in bootstrap, set it in /etc/rc.d/rc.local as:

setconf CS_LIBPATH $(getconf CS_LIBPATH):/usr/pkg/lib 

>3) Does anyone know what package mkisofs is buried in?

Maybe sysutils/cdrtools?

> 4) Doesn't It seems very odd that svn does not seem to be part of pkgsrc?   I 
> was hoping to compile the server side so as to use svn locally for my own work
>  in the future.

It is. I got confused the other day, it is not called "svn" but "subversion",
under devel :)

On Mon, Oct 01, 2007 at 01:44:58AM -0400, Mitchell Schoenbrun wrote:
> Well I think pkgsrc is wonderful.   I have some questions and
> some problems with packages to report.
> 
> 1) How can I setup my system so that /usr/pkg/bin and
> /usr/pkg/sbin are always in my PATH.4, and specifically before
> /usr/local/bin?  I know this is pretty basic.  I appologize.

I just set up my PATH in my .profile:

	PATH=/proc/boot:/bin:/usr/bin:/sbin:/usr/sbin:/usr/pkg/bin:\
/usr/pkg/sbin:/opt/bin:/usr/local/bin
# Where the following is as set up in /etc/profile.d/qnxsdk.sh
	PATH=${PATH}:${QNX_HOST}/usr/bin:\
${QNX_HOST}/usr/sbin:${QNX_HOST}/sbin:\
${QNX_HOST}/bin:${QNX_HOST}/usr/photon/appbuilder
	export PATH

> 
> 2) How can I setup my system so that /usr/pkg/lib is always
> checked for the pkgsrc libraries?  When compiling a pkgsrc package this
> seems to happen automatically, but what if I'm compiling
> my own programs?

Not sure about automatically.  These are usually the -l, -L
options to ld.

> 
> 3) Does anyone know what package mkisofs is buried in?

sysutils/cdrtools.  I suspect this may be a difficult one to
get going but I'm sure you're up to it :).

> 
> 4) Doesn't It seems very odd that svn does not seem to be part of
> pkgsrc?   I was hoping to compile the server side so as to use svn
> locally for my own work in the future.

svn is in devel/subversion-base

> 
> 5) I noticed that aclocal was not created with devel/automake.
> I don't really know what aclocal does, but it was created when
> I built automake myself.
> 
> 6) Some Problems I had with packages
> 
> www/lynx 
>     During "bmake install" the script looks for gzip in
>     /usr/bin/gzip, not /bin/gzip so if fails.  I fixed this
>     on my system by linking /bin/gzip to /usr/bin/gzip.

I'll look at this one.

> 
> devel/gettext 0.14.6
>     When doing "make install" I get the error
>         msc: illegal option -g"
>         My msc is version 1o
Does it succeed though?  I've noticed that some
configure scripts incorrectly assume mcs is a C#
compiler.
> 
> www/fcgi 2.4.0 
>     This requires -lm to compile,
>     One program gets the error
>    "undefined reference to 'frexp'"

This should be easy to fix.  I'll look into it.

> 
> devel/glib2  2.14.1
>     In the middle of the bmake, the script started downloading
>     gcc3.3.6, eek! I stopped it.  What happened here?
>     This brings up a more general question.   The default
>     compiler on my system is the 2.+ one.  Is that what it
>     should be?   Are there problems with linking objects
>     from different compilers?   How about when there are
>     shared libraries involved?
> 
> graphics/jasper
>     The script stops in bmake with message:
>         checking for C compiler default output file name... 
>         configure: error: C compiler cannot create executables
>         See 'config.log' for more details
>         I didn't find config.log helpful.
>         I don't know what jasper does, but two packages
>         I want have it as a prerequisite.
>         This is actually quite curious as I didn't
>         need it for the older versions I compiled myself.

The above two sound like you're not using 3.3.5.  Make sure
you set it as your default compiler as per the bootstrap page:
# qcc -V 3.3.5,gcc_ntox86 -set-default

> 
> 6) I noticed that there were newer versions of the packages
> devel/apr and security/openssl available on-line.   The
> newer openssl version has been around a long time, at
> least a year.

I'm sure they'll appear eventually :)  This may be
a compatibility, stability issue with other packages.

> 
> 7) In case you are interested, all of the following packages
> were built...