On 08/05/2013 12:26 AM, John R Pierce wrote:
> On 8/4/2013 3:09 PM, Ljubomir Ljubojevic wrote:
>> First try installing compiled rpm on a TEST system, and if that does not
>> work you can try recompiling the source rpm, or ask someone to help you,
>> maybe maintainer of ghostscript in Fedora.
>
> if you rebuild it via the RPM, it likely will overwrite the 'stock'
> ghostscript.
>
> a tarball install could be built to run in /usr/local/ghostscript/... or
> /opt/mystuff/ghostscript/... or whatever, and not interfere with the
> distribution build.
>
That is true if hylafax can be pointed to use optional version of
ghostcript.
If that is not the case, then ghostscript has to be replaced.
P.S. I am not a hylafax user so I can not determine what should be done.
------------------------------------------------------------------
Everyone,
Thanks so much for everyone's help !!!!
I am a new hylafax+ user and other than the ghostscript problem I am
very impressed. Hylafax+ does allow you to control the location of
ghostscript so once I get it compiled I should be able to point it to
the correct version. Instead of using the Fedora RPM, I am going to
compile it and try to route the files to a different location. I really
screwed up a different system trying to do an rpm install with a Fedora
module with a different piece of software. I am a little gun shy about
doing that again.
I am using Hylafax+ on CentOS 5.9 to replace a vsifax system installed
on SCO. If I can get ghostscript 9.07 installed properly this will be a
very good replacement.
If any of you have additional suggestions, I sure appreciate your help.
Greg
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
