kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/pkgtools/pkgdepgraph/Makefile

62 lines
1.8 KiB
Makefile
Raw Normal View History

Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.
2016-07-09 08:38:30 +02:00
# $NetBSD: Makefile,v 1.39 2016/07/09 06:38:49 wiz Exp $
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
#
Just define PKGNAME and use it.
2014-03-03 04:30:52 +01:00
PKGNAME= pkgdepgraph-2.8
Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.
2016-07-09 08:38:30 +02:00
PKGREVISION= 6
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
CATEGORIES= pkgtools devel
Reset maintainer, developer lost his commit bit.
2010-03-21 17:29:38 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Refer doc/pkgsrc.html instead of Packages.txt (HOMEPAGE variable).
2005-05-08 00:24:04 +02:00
HOMEPAGE= ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/doc/pkgsrc.html
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
COMMENT= Visual representation of installed NetBSD packages
Upgrade pkgdepgraph to 1.1. New features are: (1) Graph recoloring, so that as you delete and rebuild bunches of packages, you can see how far along you are (I use this a *lot*). (2) Subgraph grouping (based on work done by David Maxwell) which clusters groups of packages with common prefixes in their names inside a box. (3) The explicit dependency on the graphviz pkg has been removed so that pkgdepgraph can be run on "client machines" that only wish to generate graph data, not to view it (ie, machines that have packages installed but which do not wish to incur the overhead of X or the other stuff that graphviz requires). The fact that you should install graphviz *somewhere* so that you can view the data is noted by the new INSTALL script. Some useless comments have also been removed.
2002-12-26 06:40:48 +01:00
# removed so that pkgdepgraph can be used on "client" machines -- @@@
# DEPENDS+= graphviz-[0-9]*:../../graphics/graphviz
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
Move WRKSRC definition away from the first paragraph in a Makefile.
2004-01-20 13:18:15 +01:00
WRKSRC= ${WRKDIR}
Get rid of USE_PERL5. The new way to express needing the Perl executable around at either build-time or at run-time is: USE_TOOLS+= perl # build-time USE_TOOLS+= perl:run # run-time Also remove some places where perl5/buildlink3.mk was being included by a package Makefile, but all that the package wanted was the Perl executable.
2005-07-16 03:19:06 +02:00
USE_TOOLS+= perl:run
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
NO_CONFIGURE= yes
Just define PKGNAME and use it.
2014-03-03 04:30:52 +01:00
DISTVER= ${PKGVERSION_NOREV}
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
.include "../../mk/bsd.prefs.mk"
Mechanically replaced man/* with ${PKGMANDIR}/* in the definition of INSTALLATION_DIRS, as well as all occurrences of ${PREFIX}/man with ${PREFIX}/${PKGMANDIR}. Fixes PR 35265, although I did not use the patch provided therein.
2007-01-07 10:13:46 +01:00
INSTALLATION_DIRS= bin ${PKGMANDIR}/cat1 ${PKGMANDIR}/man1
Create directories before installing files into them.
2005-06-17 05:50:19 +02:00
Remove NO_PATCH, add a "do-extract" target, and tweak the "do-build" target in a related manner. This allows one to maintain local patches vs this pkg.
2002-12-29 17:25:24 +01:00
do-extract:
${CP} ${FILESDIR}/pkgdepgraph.pl ${WRKSRC}/pkgdepgraph.pl
${CP} ${FILESDIR}/pkgdepgraph.1 ${WRKSRC}/pkgdepgraph.1.in
Add a pre-generated .0 manpage; only regen under SunOS or AIX.
2004-04-11 23:29:52 +02:00
${CP} ${FILESDIR}/pkgdepgraph.0 ${WRKSRC}/pkgdepgraph.0.in
Remove NO_PATCH, add a "do-extract" target, and tweak the "do-build" target in a related manner. This allows one to maintain local patches vs this pkg.
2002-12-29 17:25:24 +01:00
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
do-build:
".for variable names should not contain uppercase letters"
2013-04-06 15:24:18 +02:00
.for file in pkgdepgraph
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
${SED} -e 's|@PREFIX@|${PREFIX}|g' \
-e 's|@PKG_DBDIR@|${PKG_DBDIR}|g' \
* Make PKGSRC_TOPDIR a private variable by renaming it to _PKGSRC_TOPDIR, as it's only used internally by bsd.prefs.mk. * Make _PKGSRCDIR a public variable by renaming it to PKGSRCDIR. Also, generate its value from ${_PKGSRC_TOPDIR} so it's less fragile than the old method of stripping off the last two components of ${.CURDIR}. PKGSRCDIR may now be used after bsd.prefs.mk is defined. * Change all references to _PKGSRCDIR to PKGSRCDIR.
2004-10-07 04:01:37 +02:00
-e 's|@PKGSRCDIR@|${PKGSRCDIR}|g' \
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
-e 's|@DISTVER@|${DISTVER}|g' \
Fixes perl interpreter path for the case using builtin perl.
2014-03-03 06:06:43 +01:00
-e 's|@PERL5@|${PERL5}|g' \
".for variable names should not contain uppercase letters"
2013-04-06 15:24:18 +02:00
< ${WRKSRC}/${file}.pl \
> ${WRKSRC}/${file}
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
.endfor
".for variable names should not contain uppercase letters"
2013-04-06 15:24:18 +02:00
.for file in pkgdepgraph.1 pkgdepgraph.0
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
${SED} -e 's|@PKG_DBDIR@|${PKG_DBDIR}|g' \
* Make PKGSRC_TOPDIR a private variable by renaming it to _PKGSRC_TOPDIR, as it's only used internally by bsd.prefs.mk. * Make _PKGSRCDIR a public variable by renaming it to PKGSRCDIR. Also, generate its value from ${_PKGSRC_TOPDIR} so it's less fragile than the old method of stripping off the last two components of ${.CURDIR}. PKGSRCDIR may now be used after bsd.prefs.mk is defined. * Change all references to _PKGSRCDIR to PKGSRCDIR.
2004-10-07 04:01:37 +02:00
-e 's|@PKGSRCDIR@|${PKGSRCDIR}|g' \
".for variable names should not contain uppercase letters"
2013-04-06 15:24:18 +02:00
< ${WRKSRC}/${file}.in \
> ${WRKSRC}/${file}
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
.endfor
do-install:
DESTDIR support
2009-02-10 01:15:20 +01:00
${INSTALL_SCRIPT} ${WRKSRC}/pkgdepgraph ${DESTDIR}${PREFIX}/bin/pkgdepgraph
Honor MANINSTALL. fixes PR#42715.
2010-02-02 11:45:59 +01:00
.if !empty(MANINSTALL:Mcatinstall)
Use CATMAN_SECTION_SUFFIX in packages which perform their own catman page installation.
2013-09-12 13:18:40 +02:00
. if defined(CATMAN_SECTION_SUFFIX) && !empty(CATMAN_SECTION_SUFFIX:M[Yy][Ee][Ss])
${INSTALL_MAN} ${WRKSRC}/pkgdepgraph.0 ${DESTDIR}${PREFIX}/${PKGMANDIR}/cat1/pkgdepgraph.1
. else
DESTDIR support
2009-02-10 01:15:20 +01:00
${INSTALL_MAN} ${WRKSRC}/pkgdepgraph.0 ${DESTDIR}${PREFIX}/${PKGMANDIR}/cat1
Use CATMAN_SECTION_SUFFIX in packages which perform their own catman page installation.
2013-09-12 13:18:40 +02:00
. endif
Honor MANINSTALL. fixes PR#42715.
2010-02-02 11:45:59 +01:00
.endif
.if !empty(MANINSTALL:Mmaninstall)
DESTDIR support
2009-02-10 01:15:20 +01:00
${INSTALL_MAN} ${WRKSRC}/pkgdepgraph.1 ${DESTDIR}${PREFIX}/${PKGMANDIR}/man1
Honor MANINSTALL. fixes PR#42715.
2010-02-02 11:45:59 +01:00
.endif
pkgdepgraph prints out a "dot" language specification of the inter-dependencies of your installed packages. The "dot" language is interpreted by the graphviz package to make graphs. There are several uses for such information. (1) A graphical representation of information is always good to look at. (2) The output itself can be sorted and filtered to provide a list of packages to delete in order that they can be rebuilt (to replace out-of-date components). (3) You can visually estimate the work involved in (or impact of) removing a given component in order to replace it.
2002-11-08 00:18:01 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink