* Make output 7-bit clean
* Add support for No. 9 and No. 6 3/4 envelopes.
* Add support for many new Avery layouts
* Add a new "orientation" setup option which can be set to "portrait"
or "landscape", with "portrait" being the default.
This switches to the new 0.6 branch which is not source compatible
to 0.5.x.
Most notable changes:
-Merge xpdf 3.02 changes
-Support for Sound objects
-Support for Opening/Closing page actions
-Support for page duration
-Improve PS Tokenizer performance
-Beginning of Interactive Form support
-xpdfrc is no longer used for anything
-Fix security issue MOAB-06-01-2007
-Lots of bugs fixed
actions on every page or on the current page. Specifically, actions
are performed after the page is composed, but before it is shipped,
so they can be used to prepare the output page in tasks like putting
watermarks in the background, setting the next page layout, etc.
then automatically generate a PLIST that says "${PKGNAME} has no files".
* If PLIST_SRC and GENERATE_PLIST are not set in a package Makefile,
and no PLIST files exist, then fail during the package build with
PKG_FAIL_REASON.
* Remove "intentionally empty" PLISTs again.
Now, the easy way to say that a package installs no files is to just
add the following to the package Makefile:
PLIST_SRC= # empty
that directly manipulate empty PLISTs.
Modify plist/plist.mk so that if the PLIST files are missing and no
GENERATE_PLIST is defined, then the package fails to build.
option in ghostscript-esp, although there it was on by default.
Here it is off by default, which is more in keeping with how the "cups" option
is generally used - it is usually off by default, and a CUPS user would
usually add "cups" to the global options.
doesn't currently pull in CUPS itself. Generally that means the
package builds without CUPS support. However, if you are
using Pkgsrc on a system with CUPS installed via some other means (E.g.
Linux with another packaging system, or even a second Pkgsrc root probably)
then things can go wrong.
I solve this case here by explicitly disabling CUPS support. For
normal cases this should mean "No change", but in exotic cases it fixes
the build and install.
Of course, there may be value in using the CUPS support, but it isn't clear
whether the right way to do that is to add a "cups" package option or to
have a second ghostscript-cups package that CUPS depends on - it kind of
looks like the latter is closer to correct at first glance.
