- Since the author decided to put a version number into his archive,
we can now safely fetch the file from his site.
- patch-ad is useless now
- updated the configure and configure.batch script, to show all possible
drivers
- install hp850 drivers license and readme file in the gs doc dir
- update the DESCR file, mention the two add on packages in this port
- The new driver supports the following additional printers:
Support for HP DeskJet 670, 690, 850, 855, 870, 890, 1100 and 1600,
See announcement on http://bonk.ethz.ch/hp850/hp850.html
Please note, that some of the drivers have certain restrictions
and produce huge output files ... Please read the release notes !!!
The author makes suggestions on his website, what driver to choose
if you need a fast printout, see
http://bonk.ethz.ch/hp850/hp850-readme.1.3.html
From: Jin Guojun (ITG staff) <jin@george.lbl.gov>
BJC-240 in color mode is supported as well by the bjc600 and bjc800 driver.
BJC-240 b&w is supported by bj200. Added this to configure dialogue.
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>:
Support for encrypted PDF files by replacing pdf_sec.ps with the
free and legal version from:
http://www.ozemail.com.au/~geoffk/pdfencrypt/pdf_sec.ps
Deceided to update the pathnames of font files for easier
maintenance, because they revamped their ftp archive structure
to "5.10/files".
Submitted by: various people
From the release notes: 5.10 is a special release to clear up
problems in the PDF writer (ps2pdf) affecting NSF's FastLane proposal
submission program: we have tested its output and verified
compatibility with the Acrobat software that NSF uses. Relative to
5.03, the only other changes in 5.10 are some improvements in the
PDF interpreter to handle more PDF 1.2 (Acrobat 3.x) constructs,
and a number of bug fixes.
See: http://bonk.ethz.ch/hp850/hp850.html
Additional driver will be fetched directly from internet now
Because this driver source is packed as a .zip file (tada *sigh*)
and contains ^M's (where the combination \^M confuses gcc) we have
to BUILD_DEPEND on unzip and pipe the source and header files through
sed to wipe out the ^M's ...
As requested by: Lars Koeller
Makefile:
- Changed WRKSRC
- New GS_SOURCES
- Make symbolic link from jpeg-6a and libpng port's workdir into
WRKSRC, instead of patching unix-gcc.mak further:
ln -s ${PORTSDIR}/graphics/jpeg/work/jpeg-6a ${WRKSRC}/jpeg-6a
ln -s ${PORTSDIR}/graphics/png/work/libpng-0.96 ${WRKSRC}/libpng
- updated md5 files
patches/patch-aa:
- new unified diff because some of the above mentioned changes
- Only commented out the default DEVICE_DEVS
- make our zlib compile again
pkg/DESCR:
- bumped version number
pkg/PLIST:
- updated PLIST
- added proper @dirrm's for a successfull pkg_delete action
scripts/configure:
- added new drivers
"la70t" "DEC LA70 printer with low resol. text enhancement" ON \
"lq850" "EPSON LQ-850 (360x360), ok for Canon BJ300 in LQ850 emul" ON \
- rmoved one unnecessary "pdfwrite"
- same for scripts/configure.batch
As requested by: Lars Koeller ;-)
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
