On Fri, 28 Aug 1998, Ken Nakata wrote:

> On Thu, 27 Aug 98 19:46:11 -0600, Jeff Woolley wrote:
> > 
> > Is the pkg_add command different than using the pkgsrc stuff, i.e., going 
> > to the directory that the package is in (cd 
> > /usr/pkgsrc/print/ghostscript5) and typing make.

> > This downloaded other packages/libs that where need for ghostscript.
> 
> What other packages/libs?  On my system, 
> 
> find /var/db/pkg -name +REQUIRED_BY | xargs fgrep ghostscript
> 
> shows nothing.  That means nothing else is required by ghostscript
> package.  Perhaps you are confusing the ghostscript source
> distribution files with other packages/libs?

It is true, that no other package is required to be INSTALLED. The package
system pulls the jpeg libs and a few other graphics libs into the build
tree, but without installing them. It also checks for the 'unzip' binary,
and will build and attempt to install the 'unzip' package if not found.
Do 'cd pkgsrc/print/ghostscript5 ; make -n build-depends,' and you will
be simply amazed.

> > I don't think it was a binary, since it was compiling it.
> 
> You're right.
> 
> > How hard is it to upgrade to 1.3.2?
> 
> I'll let others handle this, as I have never upgraded from 1.3 to
> 1.3.2.

I have patched a 1.3 source tree to build 1.3.2. The changes are fairly
minor, and have little to do with any of this.

> > It stopped in single user and said run fsck_ffs manually. I did, and 
> > answered yes for everything that was messed up.
> 
> Hmm, then some damage is done.  Maybe switching SCSI driver helps?
> (ncrscsi to sbc, or vice versa)

Why would the machine crash during a make? The drive isn't full, is it?
(Try 'df'.) When you're logged in as an ordinary user, 'make' will stop
with a "drive full" error when it comes up against the maximum free space,
but the root user bypasses that limit, and could possibly do some damage
this way.