bug: upgrade ghostscript requires running configure and faxsetup again?

Chris Coleman <[email protected]> Thu, 4 Aug 2016 19:17:19 -0400
Newsgroups gmane.comp.telephony.fax.hylafax.user
Organization Espace Networks
Message-ID <[email protected]>
Situation: "configure" generates the "faxsetup" script, which contains 
hardcoded version numbers in the PATH to the ghostscript fonts.

For example: /usr/share/ghostsrcipt/8.70/lib:/etc/ghostscript/8.70  (and 
many more paths...)

When the system upgrades ghostscript, in my case to 9.07, obviously the 
version number increases, which makes the ghostscript fonts, in those 
folders with version numbers in them, impossible to find.  So, 
"faxsetup" gives errors, it says the paths to the fonts do not exist, 
which is true, they're outdated because the embedded version number has 
increased.

Is there any way the application can be made to match on a wildcard. 
For example, /usr/share/ghostscript/?.??/lib:/etc/ghostscript/?.??

Could the application dynamically use code to pattern-match the font 
folders at runtime, so that you would no longer have to re-run 
"configure" to re-generate "faxsetup," and then force the admin to 
re-run the console interactive "faxsetup"?  Which, if they don't 
immediately do it, then outgoing faxes would fail to render text fonts 
properly, this would be a rather catastrophic scenario... and completely 
unnecessary, because smarter code can easily find the ghostscript fonts 
regardless of the version number in the path.

-Chris



-- 
---
Chris Coleman
Espace LLC
860-576-9526


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe [email protected] < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail [email protected].*