While here, remove restriction, it's "please", not "have to".
see: http://packages.debian.org/changelogs/pool/main/p/pstoedit/pstoedit_3.45-8/pstoedit.copyright
New or changed in 3.50:
* added an option (-gs) to specify the full path to GhostScript (under
Windows - either the .exe or the DLL). This can be used by portable
applications to direct pstoedit to use a specific GhostScript version.
* Stanislav Brabec contributed several improvements to the PCB driver. See
http://www.penguin.cz/~utx/pstoedit-pcb/ on how these can be useful.
* Scott Pakin submitted several improvements to the mpost driver and the
font substitution mechanism.
* new driver for .vtk files e.g. for ParaView - http://www.paraview.org/
- but this is still a very basic version. Thanks to Mitesh Patel for
initiating and testing.
* new driver for cairo (http://cairographics.org/ ) contributed by Dan
McMahill. This driver generates C-code which can be compiled and linked
against the cairo libraries. See the contrib/cairo directory for an
example.
* several improvements on the DXF driver as suggested and sponsored by
Markus Meyer.
* because pstoedit may write its output to stdout, all output written by
GhostScript to stdout is now redirected to stderr in order to avoid mixed
output.
* added a -q option to suppress the initial startup message of pstoedit.
This can by useful when being called via a pipe, e.g. from inkscape.
However, note that this does not suppress all output written to stderr -
see also note above.
* John Bowman fixed a number of problems related to clipping and image
support for the Asymptote backend.
* fixed a compilation problem with g++ V4.x.
* new driver for gcode (.ngc files) (tested with emc see
http://linuxcnc.org). Contributed by Lawrence Glaister.
* some adaptations for newer versions of libming
* fixed a line width problem for xfig format.
* corrected the broken pstoedit.m4 - thanks to Ian Abbott
* some minor code beautifying.
New or changed in 3.45:
* Some minor corrections of warnings issued by Coverity Prevent
(security related checks).
* fixed a bug in the fig backend related to dotted lines.
* added better support for pagesize handling in the driver framework.
* better handling of fonts using 0 encoded characters (thanks to
Vladimir Eltsov)
* fixed a problem which caused newer versions of GhostScript to go
into an endless loop.
New or changed in 3.44:
* hotfix for the Aysmptote driver to make it compatible with
Aysmptote version 1.00.
* removed some diagnostic messages concerning temporary file
handling.
* removed the pstoedit-config.* since this is replaced by the
pkg-config file pstoedit.pc.
New or changed in 3.43:
* some usability improvements as proposed in Debian Bug
Report #347732
[1]http://groups.google.com/group/linux.debian.bugs.dist/msg/c38e1f
79d75b3152?dmode=source&hl=de
* cleaned some minor problems found by the Klocwork checker
([2]www.klocwork.com )
* replaced tempnam with mkstemp where available.
* replaced several string related functions with the secure versions
where available (Windows - VC++2005)
* switched back again to calling GhostScript as .exe instead of via
the DLL in case pstoedit is called via gsview. Reason - there can
be only one instance of GhostScript per process and gsview needs a
second instance.
* a new driver for the OpenOffice metafile format (drvsvm)
contributed by Thorsten Behrens.
* source code cleanup considering messages issued by Gimpel's
FlexeLint/PC-Lint ([3]www.gimpel.com ).
* added a "-glyphs" option. Given this option, the PostScript
frontend passes also (if possible) the glyph names to the backend.
However, so far no backend really uses the glyph names. This is
only a preparation for future work.
* changed the way how Image/Graphicmagick is handled by configure.
Now configure tries to use pkg-config as proposed by the maintainer
of the Debian version of pstoedit (Ray Dassen).
* included a further patch for the Aysmptote driver.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
the appropriate tool via USE_TOOLS (usually "gs:run"), and remove
ghostscript.mk. This change removes a rather out-dated file from
pkgsrc and switches packages to use the more compact implementation
of the Ghostcript-handling inside the tools framework.
this way, configure will continue, even with no ghostscript installed
at build time. I realli don't want a hard dependency on a specific version.
Should fix build error seen in bulk build.
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
Reduce configure's patch size with pkgdiff.
Install documentation files in $PREFIX/share/doc/{,html/}pstoedit.
Install one file at a time.
Bump PKGREVISION.
Makefiles simply need to use this value often, for better or for
worse.
(2) Create a new variable FIX_RPATH that lists variables that should
be cleansed of -R or -rpath values if ${_USE_RPATH} is "no". By
default, FIX_RPATH contains LIBS, X11_LDFLAGS, and LDFLAGS, and
additional variables may be appended from package Makefiles.
