Net::Frame is a fork of Net::Packet. The goal here was to greatly
simplify the use of the frame crafting framework. Net::Packet does
many things undercover, and it was difficult to document all the thingies.
Also, Net::Packet may suffer from unease of use, because frames were
assembled using layers stored in L2, L3, L4 and L7 attributes. Net::Frame
removes all this, and is splitted in different modules, for those who only
want to use part of the framework, and not whole framework.
Finally, anyone can create a layer, and put it on his CPAN space, because
of the modularity Net::Frame offers. For an example,
see Net::Frame::Layer::ICMPv4 on my CPAN space.
WWW: http://search.cpan.org/dist/Net-Frame/
2007-01-09 01:55:40 +00:00
|
|
|
# New ports collection makefile for: Net-Frame
|
|
|
|
|
# Date created: 08 Jan 2007
|
|
|
|
|
# Whom: Cheng-Lung Sung <clsung@FreeBSD.org>
|
|
|
|
|
#
|
|
|
|
|
# $FreeBSD$
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
PORTNAME= Net-Frame
|
2012-02-15 06:25:55 +00:00
|
|
|
PORTVERSION= 1.09
|
Net::Frame is a fork of Net::Packet. The goal here was to greatly
simplify the use of the frame crafting framework. Net::Packet does
many things undercover, and it was difficult to document all the thingies.
Also, Net::Packet may suffer from unease of use, because frames were
assembled using layers stored in L2, L3, L4 and L7 attributes. Net::Frame
removes all this, and is splitted in different modules, for those who only
want to use part of the framework, and not whole framework.
Finally, anyone can create a layer, and put it on his CPAN space, because
of the modularity Net::Frame offers. For an example,
see Net::Frame::Layer::ICMPv4 on my CPAN space.
WWW: http://search.cpan.org/dist/Net-Frame/
2007-01-09 01:55:40 +00:00
|
|
|
CATEGORIES= net perl5
|
2008-04-17 14:30:31 +00:00
|
|
|
MASTER_SITES= CPAN
|
Net::Frame is a fork of Net::Packet. The goal here was to greatly
simplify the use of the frame crafting framework. Net::Packet does
many things undercover, and it was difficult to document all the thingies.
Also, Net::Packet may suffer from unease of use, because frames were
assembled using layers stored in L2, L3, L4 and L7 attributes. Net::Frame
removes all this, and is splitted in different modules, for those who only
want to use part of the framework, and not whole framework.
Finally, anyone can create a layer, and put it on his CPAN space, because
of the modularity Net::Frame offers. For an example,
see Net::Frame::Layer::ICMPv4 on my CPAN space.
WWW: http://search.cpan.org/dist/Net-Frame/
2007-01-09 01:55:40 +00:00
|
|
|
PKGNAMEPREFIX= p5-
|
|
|
|
|
|
2012-05-01 01:47:10 +00:00
|
|
|
MAINTAINER= perl@FreeBSD.org
|
Net::Frame is a fork of Net::Packet. The goal here was to greatly
simplify the use of the frame crafting framework. Net::Packet does
many things undercover, and it was difficult to document all the thingies.
Also, Net::Packet may suffer from unease of use, because frames were
assembled using layers stored in L2, L3, L4 and L7 attributes. Net::Frame
removes all this, and is splitted in different modules, for those who only
want to use part of the framework, and not whole framework.
Finally, anyone can create a layer, and put it on his CPAN space, because
of the modularity Net::Frame offers. For an example,
see Net::Frame::Layer::ICMPv4 on my CPAN space.
WWW: http://search.cpan.org/dist/Net-Frame/
2007-01-09 01:55:40 +00:00
|
|
|
COMMENT= Base framework for frame crafting
|
|
|
|
|
|
2012-02-15 06:25:55 +00:00
|
|
|
BUILD_DEPENDS= p5-Bit-Vector>=0:${PORTSDIR}/math/p5-Bit-Vector \
|
|
|
|
|
p5-Class-Gomor>=1.00:${PORTSDIR}/devel/p5-Class-Gomor \
|
|
|
|
|
p5-Net-IPv6Addr>=0:${PORTSDIR}/net-mgmt/p5-Net-IPv6Addr \
|
|
|
|
|
p5-Socket6>=0:${PORTSDIR}/net/p5-Socket6
|
2012-01-21 17:40:15 +00:00
|
|
|
RUN_DEPENDS:= ${BUILD_DEPENDS}
|
Net::Frame is a fork of Net::Packet. The goal here was to greatly
simplify the use of the frame crafting framework. Net::Packet does
many things undercover, and it was difficult to document all the thingies.
Also, Net::Packet may suffer from unease of use, because frames were
assembled using layers stored in L2, L3, L4 and L7 attributes. Net::Frame
removes all this, and is splitted in different modules, for those who only
want to use part of the framework, and not whole framework.
Finally, anyone can create a layer, and put it on his CPAN space, because
of the modularity Net::Frame offers. For an example,
see Net::Frame::Layer::ICMPv4 on my CPAN space.
WWW: http://search.cpan.org/dist/Net-Frame/
2007-01-09 01:55:40 +00:00
|
|
|
|
|
|
|
|
PERL_CONFIGURE= yes
|
|
|
|
|
|
|
|
|
|
MAN3= Net::Frame.3 Net::Frame::Layer.3 \
|
|
|
|
|
Net::Frame::Layer::ARP.3 \
|
|
|
|
|
Net::Frame::Layer::ETH.3 \
|
|
|
|
|
Net::Frame::Layer::IPv4.3 \
|
|
|
|
|
Net::Frame::Layer::NULL.3 \
|
|
|
|
|
Net::Frame::Layer::PPP.3 \
|
|
|
|
|
Net::Frame::Layer::RAW.3 \
|
|
|
|
|
Net::Frame::Layer::SLL.3 \
|
|
|
|
|
Net::Frame::Layer::TCP.3 \
|
|
|
|
|
Net::Frame::Layer::UDP.3
|
|
|
|
|
|
2007-03-28 02:26:35 +00:00
|
|
|
.include <bsd.port.mk>
|
