Subject: pkg/10181: ghostscript package appears to have been committed w/o testing
To: None <>
From: None <>
List: netbsd-bugs
Date: 05/23/2000 08:20:12
>Number:         10181
>Category:       pkg
>Synopsis:       The "ghostscript" package is hosed by its vflib "support"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 23 08:21:00 PDT 2000
>Release:        pkgsrc as of 2000-05-23 on -current as of 2000-05-22
	Stevens Institute of Technology
System: NetBSD 1.4Y NetBSD 1.4Y (BOCK) #1: Fri May 19 16:54:47 EDT 2000 root@lamneth:/usr/src/sys/arch/i386/compile/BOCK i386

The "ghostscript" package compiles, but that's about all it does.
It doesn't appear to have ever been tested *at all* prior to committing.
Multiple serious problems make it essentially unusable in its current
condition.  These problems include:

	* PLIST build screwed up: the essential "vflib" directory is
	  omitted, which causes an immediate interpreter abort upon
	  invocation if the package has been installed from the

	* Even if the above problem does not appear (e.g. because the
	  package was built from source) the interpreter aborts
	  after processing the first VFlib initialization file, as

Aladdin Ghostscript 6.01 (2000-03-17)
Copyright (C) 2000 Aladdin Enterprises, Menlo Park, CA.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Loading Times-Roman font from /usr/pkg/share/ghostscript/fonts/ix/Times-Roman... 4938212 3566938 1556964 261536 0 done.
Loading Helvetica font from /usr/pkg/share/ghostscript/fonts/ix/Helvetica... 5256316 3840541 1577060 269108 0 done.
Aladdin Ghostscript 6.01: VFlib: Cannot open the font `min'.
Unrecoverable error: unknownerror in kfVFlib
Operand stack:
    min  0  10273  0  10273  c21  Private

	 * The `min' font does not appear to exist *anywhere* in
	   pkgsrc.  If the maintainer of the ghostscript package
	   actually tested the changes which have caused this chaos,
	   I can only suggest that he must have had the required
	   VFlib files (.ps files, `min' font) somewhere else on his
	   system which happened to be in either Ghostscript or
	   VFlib's search path.

	To exhibit the first problem, build the "ghostscript" package
	and then install it on another system from the tarball.  No
	vflib, so BOOM.

	To exhibit the second problem, build the "ghostscript" package
	and then install it from source (NOT the tarball) on a system
	without any VFlib support or Japanese fonts somewhere else
	where VFlib or GhostScript will find them.  BOOM.

	One workaround is obvious: remove the VFlib support which has
	broken ghostscript for all users.  I am hesitant to do this
	since if I only knew where to *get* the right fonts, it should
	not be too difficult to fix the package to work as intended.

	Unfortunately, I do not, so I can only hope that the package
	maintainer will do so in an expeditious fashion.