ghostscript installation

[mikebw at colossus.bilow.com (Mike Bilow)]

The filesystem standard tries to account for package managers by proving
the "local" spaces for users to install things that are guaranteed not to
collide with things under the control of a package manager.

If you are really stuck because someone hardcoded a path into ancient
software, just make a symlink.

-- Mike


On Fri, 31 Mar 2000 dmoylan at ibm.net wrote:

> on a redhat 5.2 system, i replaced gs4.03 with a new download of gs5.50,
> and compiled and installed it.
> 
> the original set up had
> 	- binaries in /usr/bin, 
> 	- supporting stuff in /usr/share/ghostscript/4.03
> the new set up has
> 	- binaries in /usr/local/bin, 
> 	- supporting stuff in /usr/local/share/ghostscript/5.50
> 
> running gs from the command line seems to work fine, as /usr/local/bin
> is in my path.
> 
> printtool, however, does not find ghostscript, and the printer as a 
> consequence, does not function.  
> 
> what do i need to do?
> 
> tia,
> dan


-
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).