Path to this page:
./
fonts/ghostscript-cmaps,
CMap resources for Ghostscript
Branch: CURRENT,
Version: 20020913nb3,
Package name: ghostscript-cmaps-20020913nb3,
Maintainer: pkgsrc-usersThis package enables Ghostscript to use the CMap files provided in the
adobe-cmaps package.
DEINSTALL [+/-]#!/bin/sh
#
# $NetBSD: DEINSTALL,v 1.1 2006/06/15 20:40:15 jlam Exp $
ADOBE_RESOURCEDIR="@ADOBE_RESOURCEDIR@"
GS_RESOURCEDIR="@GS_RESOURCEDIR@"
PKG_INFO="@PKG_INFO@"
case ${STAGE} in
DEINSTALL)
${PKG_INFO} -qL adobe-cmaps | ${GREP} "/Resource/CMap/" |
while read src; do
base=`${BASENAME} $src`
dest="${GS_RESOURCEDIR}/CMap/$base"
${RM} -f $dest
done
;;
esac
Required to run:[
print/ghostscript]
Required to build:[
pkgtools/cwrappers]
Version history: (Expand)
- (2017-11-23) Package has been reborn
- (2013-04-24) Updated to version: ghostscript-cmaps-20020913nb3
- (2012-06-11) Package has been reborn
- (2012-06-11) Package deleted from pkgsrc
- (2006-02-06) Updated to version: ghostscript-cmaps-20020913nb2
- (2005-10-05) Package added to pkgsrc.se, version ghostscript-cmaps-20020913nb1 (created)
CVS history: (Expand)
2013-04-24 12:06:53 by Steven Drake | Files touched by this commit (38) |
Log message:
Revbump for all packages that have USE_TOOLS+=gs
|
2012-10-03 20:28:33 by Aleksej Saushev | Files touched by this commit (154) |
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
|
2009-04-09 02:48:18 by Joerg Sonnenberger | Files touched by this commit (109) |
Log message:
Remove redundant NO_CHECKSUM and EXTRACT_ONLY definitions.
|
2008-06-20 03:09:45 by Joerg Sonnenberger | Files touched by this commit (993) |
Log message:
Add DESTDIR support.
|
2006-09-02 22:37:00 by Roland Illig | Files touched by this commit (1) |
Log message:
No distinfo file needed.
|
2006-06-15 22:40:16 by Johnny C. Lam | Files touched by this commit (37) |
Log message:
Split out deinstall portions of INSTALL scripts into DEINSTALL scripts.
This avoids the need for a confusing line of the form:
DEINSTALL_TEMPLATE+= path/to/INSTALL
in the package Makefile, and actually removes the need to specify it
altogether since by convention, the existence of the DEINSTALL script
is enough to add it to DEINSTALL_TEMPLATE.
|
2006-03-14 02:14:36 by Johnny C. Lam | Files touched by this commit (134) |
Log message:
Modify the pkginstall framework so that it manages all aspects of
INSTALL/DEINSTALL script creation within pkgsrc.
If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts. If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:
INSTALL_SRC= ${PKGDIR}/INSTALL
DEINSTALL_SRC= # emtpy
As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts. By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).
In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework. The only public variables relating to the templates are:
INSTALL_SRC INSTALL_TEMPLATE
DEINSTALL_SRC DEINSTALL_TEMPLATE
HEADER_TEMPLATE
The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
|
2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257) |
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
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.
|