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

65 lines
1.6 KiB
Makefile
Raw Normal View History

s/netbsd.org/NetBSD.org/
2003-07-18 00:50:55 +02:00
# $NetBSD: Makefile,v 1.12 2003/07/17 22:52:17 grant 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
#
Add a new -m option that prints sh script which invokes make for each "interesting" package, where "interesting" is defined by the other options given on the command line. Rework the "rebuild", "delete", and "fetch" output modes to use a new generic routine invoked with (the new) -m option. Other new options are: -a all packages (to make more packages becoming "interesting") -e adds an "existence check" to each of the lines of sh(1) style output (ala the current rebuild output) -r reverses the order in which the packages are listed -S package selects a subgraph of the installed package base -s print a simple list of packages instead of sh commands Also: fix a dreadful bug in the group number assignment loop. Groups are now assigned more properly, meaning that wholely selected subgraphs (via the new -S option) work. Welcome to version 2.5.
2003-04-30 05:39:17 +02:00
DISTNAME= pkgdepgraph-2.5
Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.
2003-03-29 13:40:00 +01:00
WRKSRC= ${WRKDIR}
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
MASTER_SITES= # empty
DISTFILES= # empty
s/netbsd.org/NetBSD.org/
2003-07-18 00:50:55 +02:00
MAINTAINER= atatat@NetBSD.org
HOMEPAGE= ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/Packages.txt
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
USE_PERL5= YES
EXTRACT_ONLY= # empty
NO_CHECKSUM= yes
NO_CONFIGURE= yes
DISTVER= ${DISTNAME:S/pkgdepgraph-//}
.include "../../mk/bsd.prefs.mk"
.if ${OPSYS} == "SunOS"
# This doesn't create readable manual pages. "mandoc" should be added
# to zoularis.
NROFF= nroff -man
.else
NROFF= nroff -mandoc
.endif
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
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 FILE in pkgdepgraph
${SED} -e 's|@PREFIX@|${PREFIX}|g' \
-e 's|@PKG_DBDIR@|${PKG_DBDIR}|g' \
Jump to pkgdepgraph v2.0. New features (excerpts from the man page, not in proper order, so that you can better see how it fits together): -L Limit the graph to those packages that are out of date or ulti- mately depend on some package that is. -D Instead of the standard graph output, pkgdepgraph lists the packages that need to be deleted, in ``least required first'' order, so that they can be deleted without any dependency prob- lems. -R Instead of the standard graph output, emits a series of sh(1) commands that will rebuild all the out of date packages by re- building all the deleted leaf packages. -U package Generates a graph with only the out of date dependencies of package marked in red (ie, packages that are out of date but not dependencies of package will not be considered out of date). -f Force a rebuild of all dependent packages. This option is for use in conjunction with the -U option to force a rebuild of all the dependencies of a package to be updated. -O package Marks package as out of date so that you can see the impact of deleting dependent packages and rebuilding everything. -t target Changes the target of the -R output from ``install'' to target in case you want to ``make package'' or some other target. -c Inserts a ``make clean'' command in the set of instructions to rebuild packages (see the -R option) after they are installed. -C Asserts -c and adds ``CLEANDEPENDS=YES'' so that all rebuilt de- pendencies are cleaned as well. The code was also cleaned up a bit, some unused or otherwise useless variables were culled, the "multiple box" phenomenon of subgroups is fixed, and the examples were all cleaned up to take advantage of all the new features. Hey ma! Now I can update my pkgs in four easy steps! $ lintpkgsrc -i > pkgdepgraph.in $ pkgdepgraph -R pkgdepgraph.in > rebuild.sh $ pkg_delete `pkgdepgraph -D pkgdepgraph.in` $ sh rebuild.sh
2003-03-06 22:13:13 +01: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' \
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
< ${WRKSRC}/${FILE}.pl \
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
> ${WRKSRC}/${FILE}
.endfor
.for FILE in pkgdepgraph
${SED} -e 's|@PKG_DBDIR@|${PKG_DBDIR}|g' \
Jump to pkgdepgraph v2.0. New features (excerpts from the man page, not in proper order, so that you can better see how it fits together): -L Limit the graph to those packages that are out of date or ulti- mately depend on some package that is. -D Instead of the standard graph output, pkgdepgraph lists the packages that need to be deleted, in ``least required first'' order, so that they can be deleted without any dependency prob- lems. -R Instead of the standard graph output, emits a series of sh(1) commands that will rebuild all the out of date packages by re- building all the deleted leaf packages. -U package Generates a graph with only the out of date dependencies of package marked in red (ie, packages that are out of date but not dependencies of package will not be considered out of date). -f Force a rebuild of all dependent packages. This option is for use in conjunction with the -U option to force a rebuild of all the dependencies of a package to be updated. -O package Marks package as out of date so that you can see the impact of deleting dependent packages and rebuilding everything. -t target Changes the target of the -R output from ``install'' to target in case you want to ``make package'' or some other target. -c Inserts a ``make clean'' command in the set of instructions to rebuild packages (see the -R option) after they are installed. -C Asserts -c and adds ``CLEANDEPENDS=YES'' so that all rebuilt de- pendencies are cleaned as well. The code was also cleaned up a bit, some unused or otherwise useless variables were culled, the "multiple box" phenomenon of subgroups is fixed, and the examples were all cleaned up to take advantage of all the new features. Hey ma! Now I can update my pkgs in four easy steps! $ lintpkgsrc -i > pkgdepgraph.in $ pkgdepgraph -R pkgdepgraph.in > rebuild.sh $ pkg_delete `pkgdepgraph -D pkgdepgraph.in` $ sh rebuild.sh
2003-03-06 22:13:13 +01:00
-e 's|@PKGSRCDIR@|${_PKGSRCDIR}|g' \
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
< ${WRKSRC}/${FILE}.1.in \
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
> ${WRKSRC}/${FILE}.1
${NROFF} ${WRKSRC}/${FILE}.1 >${WRKSRC}/${FILE}.0
.endfor
do-install:
${INSTALL_SCRIPT} ${WRKSRC}/pkgdepgraph ${PREFIX}/bin/pkgdepgraph
${INSTALL_MAN} ${WRKSRC}/pkgdepgraph.0 ${PREFIX}/man/cat1
${INSTALL_MAN} ${WRKSRC}/pkgdepgraph.1 ${PREFIX}/man/man1
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
post-install:
@${SH} ${INSTALL_FILE} ${PKGNAME} POST-INSTALL
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