FreeBSD Port: ghostscript-gnu-7.07

Rob Lahaye lahaye at snu.ac.kr
Sun Jul 13 20:40:08 PDT 2003


Stacey Roberts wrote:
> 
> Hello,
> 
> On Sun, 2003-07-13 at 04:22, Rob Lahaye wrote:
> 
>>Stacey Roberts wrote:
>>
>>>
>>>I was getting this failure last night as well, but has just this minute
>>>worked for me as part of portupgrading Gnome-2.
>>>
>>>Have a go.
>>
>>Nope, still same problems occur.
> 
> 
> Shame, try manually pulling down the file from the suggested ftp site
> into /usr/ports/distfiles, then retry.

That worked, but only by also the modifying the MD5 sum of "Samsung-SmartGDI-all-GS.tar.gz"
in distfiles. This is not a clean port upgrade. Please fix.

By the way: I suppose this upgrade does not address the printer problem as arose
from a discussion between me and Glenn Johnson:

-----------------------
Subject: CUPS and HP LaserJet 4V printer: variable width font becomes fixed width

 > Glenn Johnson <gjohnson at srrc.ars.usda.gov> wrote:
 >
 >>> > On Fri, Jun 20, 2003 at 05:59:10PM +0900, Rob Lahaye wrote:
 >>
 >>>> Since I have upgraded to FreeBSD 4.8 (with cups-1.1.18), printing
 >>>> has a problem with variable width fonts. Variable width fonts are
 >>>> printed out as fixed width fonts; so text looks ugly and runs over
 >>>> the lines.
 >>
 >>> Are you using an "up-to-date" version of ghostscript?  If so, that
 >>> is the problem.  The last version of ghostscript that does not
 >>> exhibit this problem is ghostscript-gnu-7.05_5.  I am not sure
 >>> about the version number of ghostscript-afpl but recent versions
 >>> exhibit this problem.
 >>
 >> Yes I was up-to-date with ghostscript and that indeed was the problem.
 >> I forced the deinstall of my ghostscript-gnu-7.07, and installed
 >> instead from the packages, version 7.05_4.
 >> And my printing problem has gone now! Thanks.
 >>
 >> Is the origin of the problem located? Will it be fixed in the next
 >> release of ghostscript-gnu? Has this problem been reported to the
 >> ghostscript-gnu developer community?
 >
 > I am not sure but I believe the problem is specific to the FreeBSD
 > ports.  I hope to have some time this weekend to dig into it a bit.
-----------------------


Regards,
Rob.



More information about the freebsd-ports mailing list