kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/net/flowscan/Makefile

73 lines
2.6 KiB
Makefile
Raw Normal View History

Decapitalise FlowScan. FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 02:14:44 +01:00
# New ports collection makefile for: flowscan
FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 00:20:57 +01:00
# Date created: Di 13 M<>r 2001 08:23:55 CET
# Whom: andreas@freebsd.org
#
# $FreeBSD$
#
Decapitalise FlowScan. FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 02:14:44 +01:00
PORTNAME= flowscan
FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 00:20:57 +01:00
PORTVERSION= 1.006
- detected, that the graphs/Makefile.sample isn't bmake friendly we need gmake here, added it to run dependencies therefore updated PORTREVISION, otherwise you don't get the png file... - updated pkg-message. You need to configure SNMP on your cisco or Juniper router
2001-03-25 18:56:55 +02:00
PORTREVISION= 5
FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 00:20:57 +01:00
CATEGORIES= net
Unjoin lines that were (accidentally?) joined in rev 1.3 Submitted by: distfile survey
2001-03-18 01:27:16 +01:00
MASTER_SITES= http://net.doit.wisc.edu/~plonka/FlowScan/
DISTFILES= FlowScan-${PORTVERSION}.tar.gz
FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 00:20:57 +01:00
sorry, no time for maintenance, hand port over to ports team entirely
2001-07-06 12:35:32 +02:00
MAINTAINER= ports@FreeBSD.org
FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 00:20:57 +01:00
BUILD_DEPENDS= ksh:${PORTSDIR}/shells/pdksh \
rrdtool:${PORTSDIR}/net/rrdtool \
A user (bento for example) may not have ${LOCALBASE}/sbin in his PATH, so use explicit path to the dependency instead of just executable name. Submitted by: bento
2001-03-20 11:08:43 +01:00
${LOCALBASE}/sbin/cflowd:${PORTSDIR}/net/cflowd \
Typo (converter -> converters). Submitted by: bento
2001-03-21 18:48:55 +01:00
${LOCALBASE}/lib/perl5/site_perl/${PERL_VER}/Boulder/Stream.pm:${PORTSDIR}/converters/p5-Boulder \
fix package making, one more: ${{ -> ${
2001-03-25 11:20:58 +02:00
${LOCALBASE}/lib/perl5/site_perl/${PERL_VER}/ConfigReader/DirectiveStyle.pm:${PORTSDIR}/devel/p5-ConfigReader \
FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 00:20:57 +01:00
${LOCALBASE}/lib/perl5/site_perl/${PERL_VER}/HTML/Table.pm:${PORTSDIR}/www/p5-HTML-Table \
- fix another showstopper, forgot a "\" at the end of the previous build dependency.
2001-03-26 01:52:12 +02:00
${LOCALBASE}/lib/perl5/site_perl/${PERL_VER}/${PERL_ARCH}/Cflow.pm:${PORTSDIR}/net/p5-Cflow \
another show stopper, missing dependency to p5-Net-Patricia didn't bump PORTREVISION, since package building has been impossible
2001-03-26 00:06:39 +02:00
${LOCALBASE}/lib/perl5/site_perl/${PERL_VER}/${PERL_ARCH}/Net/Patricia.pm:${PORTSDIR}/net/p5-Net-Patricia
- detected, that the graphs/Makefile.sample isn't bmake friendly we need gmake here, added it to run dependencies therefore updated PORTREVISION, otherwise you don't get the png file... - updated pkg-message. You need to configure SNMP on your cisco or Juniper router
2001-03-25 18:56:55 +02:00
RUN_DEPENDS= gmake:${PORTSDIR}/devel/gmake
FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 00:20:57 +01:00
CFLOWD_FLOWSCAN_PATCH= yes
HAS_CONFIGURE= yes
- completely new functionalities, so bumped port revision this was overdue, since this complex port needs more docu, explanation, preparation, etc ... - installation directory moved from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows to match our typical /var filesystem layout, but since I want to package this port, I don't want to write into /var/filesystem its up to the user, to move the data around later if he has a large /var and likes the data to reside there. - create needed directories in ${PREFIX}/var/db/flows (bin and graphs) use a .keep_me file, so that things are packaged properly - install needed documentation the INSTALL file is essential as well as the various example file. NOPORTDOCS only covers unneeded files, which are not crucial for installation - the ${PREFIX}/var/db/flows/bin directory carries the sample files for the flowscan script. Therefore those sample files reside there. Other sample files like the crontab settings are up to the user, so they reside in ${PREFIX}/share/doc/flowscan - install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since this is a port that needs thinking and handcrafting config files before use... - added a pkg-message file, that explains pre-requisites (cisco configuration) and other post installation tasks as well as a BIG WARNING, that enabling Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION routers might affect the routers switching performance. You should know IF you need to do it and if its o.k. IF you enable it. - output pkg-message on port based installation as well since the warnings are important. - updated PLIST
2001-03-25 13:48:48 +02:00
CONFIGURE_ARGS+= --prefix=${PREFIX}/var/db/flows
unbreak port even more... we also need to redefine WRKSRC because of this lowercase affair... which I start to dislike, because if poeple learn about a software named FlowScan, then they start looking for a port named FlowScan and not flowscan ... no portrevision bump necessary, since port didn't work properly.
2001-03-15 08:56:55 +01:00
WRKSRC= ${WRKDIR}/FlowScan-${PORTVERSION}
FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 00:20:57 +01:00
pre-install:
portlintify
2001-03-25 22:41:45 +02:00
@ ${MKDIR} ${PREFIX}/var/db/flows/bin
@ ${MKDIR} ${PREFIX}/var/db/flows/graphs
- completely new functionalities, so bumped port revision this was overdue, since this complex port needs more docu, explanation, preparation, etc ... - installation directory moved from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows to match our typical /var filesystem layout, but since I want to package this port, I don't want to write into /var/filesystem its up to the user, to move the data around later if he has a large /var and likes the data to reside there. - create needed directories in ${PREFIX}/var/db/flows (bin and graphs) use a .keep_me file, so that things are packaged properly - install needed documentation the INSTALL file is essential as well as the various example file. NOPORTDOCS only covers unneeded files, which are not crucial for installation - the ${PREFIX}/var/db/flows/bin directory carries the sample files for the flowscan script. Therefore those sample files reside there. Other sample files like the crontab settings are up to the user, so they reside in ${PREFIX}/share/doc/flowscan - install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since this is a port that needs thinking and handcrafting config files before use... - added a pkg-message file, that explains pre-requisites (cisco configuration) and other post installation tasks as well as a BIG WARNING, that enabling Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION routers might affect the routers switching performance. You should know IF you need to do it and if its o.k. IF you enable it. - output pkg-message on port based installation as well since the warnings are important. - updated PLIST
2001-03-25 13:48:48 +02:00
post-install:
portlintify
2001-03-25 22:41:45 +02:00
# sample startup script
- completely new functionalities, so bumped port revision this was overdue, since this complex port needs more docu, explanation, preparation, etc ... - installation directory moved from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows to match our typical /var filesystem layout, but since I want to package this port, I don't want to write into /var/filesystem its up to the user, to move the data around later if he has a large /var and likes the data to reside there. - create needed directories in ${PREFIX}/var/db/flows (bin and graphs) use a .keep_me file, so that things are packaged properly - install needed documentation the INSTALL file is essential as well as the various example file. NOPORTDOCS only covers unneeded files, which are not crucial for installation - the ${PREFIX}/var/db/flows/bin directory carries the sample files for the flowscan script. Therefore those sample files reside there. Other sample files like the crontab settings are up to the user, so they reside in ${PREFIX}/share/doc/flowscan - install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since this is a port that needs thinking and handcrafting config files before use... - added a pkg-message file, that explains pre-requisites (cisco configuration) and other post installation tasks as well as a BIG WARNING, that enabling Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION routers might affect the routers switching performance. You should know IF you need to do it and if its o.k. IF you enable it. - output pkg-message on port based installation as well since the warnings are important. - updated PLIST
2001-03-25 13:48:48 +02:00
@ ${INSTALL_SCRIPT} ${FILESDIR}/flowscan.sh \
- bump portrevision because important features were added to port to make it more functional and userfriendly - added cflowd's startup script to FILESDIR, add startup options to it, that are only valid for the patched cflowd. So later we overwrite the sample startup script of "stock" cflowd. This is done this way, because cflowd also can be used without flowscan. But *if* we use cflowd with flowscan, we have to manage things to work with flowscan. - install sample Makefile to graphs directory, so you can generate graphs more easily as being described in the docu (see INSTALL) - Added comments to pkg-message file, that this Makefile has to be updated whenever you add or remove protocol types in ${PREFIX}/var/db/flows/bin/CampusIO.cf - comment post-install section more.. - keep_me file could be removed, since we install the sample Makefile now in the graphs subdir
2001-03-25 17:54:48 +02:00
${PREFIX}/etc/rc.d/cflowd-flowscan.sh.sample
# overwrite cflowd startup script, since we need some additional
# parameters !
@ ${INSTALL_SCRIPT} ${FILESDIR}/cflowd.sh \
${PREFIX}/etc/rc.d/cflowd-base.sh.sample
portlintify
2001-03-25 22:41:45 +02:00
# sample Makefile to generate graphs
- bump portrevision because important features were added to port to make it more functional and userfriendly - added cflowd's startup script to FILESDIR, add startup options to it, that are only valid for the patched cflowd. So later we overwrite the sample startup script of "stock" cflowd. This is done this way, because cflowd also can be used without flowscan. But *if* we use cflowd with flowscan, we have to manage things to work with flowscan. - install sample Makefile to graphs directory, so you can generate graphs more easily as being described in the docu (see INSTALL) - Added comments to pkg-message file, that this Makefile has to be updated whenever you add or remove protocol types in ${PREFIX}/var/db/flows/bin/CampusIO.cf - comment post-install section more.. - keep_me file could be removed, since we install the sample Makefile now in the graphs subdir
2001-03-25 17:54:48 +02:00
@ ${INSTALL_DATA} ${WRKSRC}/graphs.mf \
${PREFIX}/var/db/flows/graphs/Makefile.sample
portlintify
2001-03-25 22:41:45 +02:00
# sample config files
- completely new functionalities, so bumped port revision this was overdue, since this complex port needs more docu, explanation, preparation, etc ... - installation directory moved from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows to match our typical /var filesystem layout, but since I want to package this port, I don't want to write into /var/filesystem its up to the user, to move the data around later if he has a large /var and likes the data to reside there. - create needed directories in ${PREFIX}/var/db/flows (bin and graphs) use a .keep_me file, so that things are packaged properly - install needed documentation the INSTALL file is essential as well as the various example file. NOPORTDOCS only covers unneeded files, which are not crucial for installation - the ${PREFIX}/var/db/flows/bin directory carries the sample files for the flowscan script. Therefore those sample files reside there. Other sample files like the crontab settings are up to the user, so they reside in ${PREFIX}/share/doc/flowscan - install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since this is a port that needs thinking and handcrafting config files before use... - added a pkg-message file, that explains pre-requisites (cisco configuration) and other post installation tasks as well as a BIG WARNING, that enabling Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION routers might affect the routers switching performance. You should know IF you need to do it and if its o.k. IF you enable it. - output pkg-message on port based installation as well since the warnings are important. - updated PLIST
2001-03-25 13:48:48 +02:00
.for i in CampusIO.cf Napster_subnets.boulder SubNetIO.cf flowscan.cf \
local_nets.boulder our_subnets.boulder
@ ${INSTALL_DATA} ${WRKSRC}/cf/${i} \
${PREFIX}/var/db/flows/bin/${i}.sample
.endfor
portlintify
2001-03-25 22:41:45 +02:00
# important docu files
@ ${MKDIR} ${PREFIX}/share/doc/flowscan
- completely new functionalities, so bumped port revision this was overdue, since this complex port needs more docu, explanation, preparation, etc ... - installation directory moved from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows to match our typical /var filesystem layout, but since I want to package this port, I don't want to write into /var/filesystem its up to the user, to move the data around later if he has a large /var and likes the data to reside there. - create needed directories in ${PREFIX}/var/db/flows (bin and graphs) use a .keep_me file, so that things are packaged properly - install needed documentation the INSTALL file is essential as well as the various example file. NOPORTDOCS only covers unneeded files, which are not crucial for installation - the ${PREFIX}/var/db/flows/bin directory carries the sample files for the flowscan script. Therefore those sample files reside there. Other sample files like the crontab settings are up to the user, so they reside in ${PREFIX}/share/doc/flowscan - install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since this is a port that needs thinking and handcrafting config files before use... - added a pkg-message file, that explains pre-requisites (cisco configuration) and other post installation tasks as well as a BIG WARNING, that enabling Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION routers might affect the routers switching performance. You should know IF you need to do it and if its o.k. IF you enable it. - output pkg-message on port based installation as well since the warnings are important. - updated PLIST
2001-03-25 13:48:48 +02:00
@ ${INSTALL_DATA} ${WRKSRC}/example/crontab \
${PREFIX}/share/doc/flowscan/crontab.sample
@ ${INSTALL_DATA} ${WRKSRC}/rc/linux/cflowd \
${PREFIX}/share/doc/flowscan/cflowd.sample
@ ${INSTALL_DATA} ${WRKSRC}/rc/linux/flowscan \
${PREFIX}/share/doc/flowscan/flowscan.sample
@ ${INSTALL_DATA} ${WRKSRC}/INSTALL ${PREFIX}/share/doc/flowscan
portlintify
2001-03-25 22:41:45 +02:00
# less important docu files
- completely new functionalities, so bumped port revision this was overdue, since this complex port needs more docu, explanation, preparation, etc ... - installation directory moved from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows to match our typical /var filesystem layout, but since I want to package this port, I don't want to write into /var/filesystem its up to the user, to move the data around later if he has a large /var and likes the data to reside there. - create needed directories in ${PREFIX}/var/db/flows (bin and graphs) use a .keep_me file, so that things are packaged properly - install needed documentation the INSTALL file is essential as well as the various example file. NOPORTDOCS only covers unneeded files, which are not crucial for installation - the ${PREFIX}/var/db/flows/bin directory carries the sample files for the flowscan script. Therefore those sample files reside there. Other sample files like the crontab settings are up to the user, so they reside in ${PREFIX}/share/doc/flowscan - install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since this is a port that needs thinking and handcrafting config files before use... - added a pkg-message file, that explains pre-requisites (cisco configuration) and other post installation tasks as well as a BIG WARNING, that enabling Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION routers might affect the routers switching performance. You should know IF you need to do it and if its o.k. IF you enable it. - output pkg-message on port based installation as well since the warnings are important. - updated PLIST
2001-03-25 13:48:48 +02:00
.if !defined(NOPORTDOCS)
@ ${ECHO_MSG} "===> Installing documentation for ${PKGNAME}"
.for i in README README.html INSTALL.html TODO
@ ${INSTALL_DATA} ${WRKSRC}/${i} ${PREFIX}/share/doc/flowscan
.endfor
.endif
portlintify
2001-03-25 22:41:45 +02:00
# info
@ ${CAT} ${.CURDIR}/pkg-message
FlowScan is a tool to monitor and graph flow information from Cisco and Riverstone routers in near real-time. Amonst many other things, FlowScan can measure and graph traffic for applications such as Napster. A sample of what FlowScan can do is at: http://wwwstats.net.wisc.edu WWW: http://net.doit.wisc.edu/~plonka/FlowScan/
2001-03-14 00:20:57 +01:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink