ghostscript installation
Mark J. Dulcey
mark at buttery.org
Fri Mar 31 09:54:29 EST 2000
On Fri, 31 Mar 2000, Lars Kellogg-Stedman wrote:
> On Fri, 31 Mar 2000 dmoylan at ibm.net wrote:
>
> > the new set up has
> > - binaries in /usr/local/bin,
> > - supporting stuff in /usr/local/share/ghostscript/5.50
>
> I detest RPMs with this particular problem; at least on my own system, I
> prefer /usr/local to be things I've built myself, and /usr to me
> rpm-installed packages. It makes management much easier.
>
> My first suggestion would be to look for an RPM that doesn't insist on
> dropping things in /usr/local.
>
> > printtool, however, does not find ghostscript, and the printer as a
> > consequence, does not function.
>
> There are several solutions; the simplest is probably to create a symbolic
> link in /usr/bin for gs:
>
> ln -s /usr/local/bin/gs /usr/bin/gs
>
> When printtool looks for /usr/bin/gs it will find it.
>
> Since you need to be root to run printtool, you may want to be sure that
> /usr/local/bin is in *root's* PATH.
The problem isn't merely that printtool doesn't find gs; the problem is
that the whole smart filter package expects it to be in the usual place.
If it were just a problem with printtool, it would be easy enough to
change the code - it's a Tcl/Tk package, so everybody has the source
installed.
--
Mark J. Dulcey mark at buttery.org
Visit my house's home page: http://www.buttery.org/
Visit my home page: http://www.buttery.org/markpoly/
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).
More information about the Discuss
mailing list