kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/www/p5-Parse-HTTP-UserAgent/Makefile

26 lines
538 B
Makefile
Raw Normal View History

- Cleanup Makefile header
2013-08-21 19:42:57 +02:00
# Created by: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>
- Add p5-Parse-HTTP-UserAgent 0.32 Parse::HTTP::UserAgent implements a rules-based parser and tries to identify MSIE, FireFox, Opera, Safari & Chrome first. It then tries to identify Mozilla, Netscape, Robots and the rest will be tried with a generic parser. There is also a structure dumper, useful for debugging. User agent strings are a complete mess since there is no standard format for them. They can be in various formats and can include more or less information depending on the vendor's (or the user's) choice. Also, it is not dependable since it is some arbitrary identification string. Any user agent can fake another. So, why deal with such a useless mess? You may want to see the choice of your visitors and can get some reliable data (even if some are fake) and generate some nice charts out of them or just want to send an HttpOnly cookie if the user agent seems to support it (and send a normal one if this is not the case). However, browser sniffing for client-side coding is considered a bad habit. WWW: http://search.cpan.org/dist/Parse-HTTP-UserAgent/ Feature safe: yes
2011-11-12 17:45:51 +01:00
# $FreeBSD$
PORTNAME= Parse-HTTP-UserAgent
- Update to 0.39 Changes: http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes
2013-12-02 10:16:41 +01:00
PORTVERSION= 0.39
- Add p5-Parse-HTTP-UserAgent 0.32 Parse::HTTP::UserAgent implements a rules-based parser and tries to identify MSIE, FireFox, Opera, Safari & Chrome first. It then tries to identify Mozilla, Netscape, Robots and the rest will be tried with a generic parser. There is also a structure dumper, useful for debugging. User agent strings are a complete mess since there is no standard format for them. They can be in various formats and can include more or less information depending on the vendor's (or the user's) choice. Also, it is not dependable since it is some arbitrary identification string. Any user agent can fake another. So, why deal with such a useless mess? You may want to see the choice of your visitors and can get some reliable data (even if some are fake) and generate some nice charts out of them or just want to send an HttpOnly cookie if the user agent seems to support it (and send a normal one if this is not the case). However, browser sniffing for client-side coding is considered a bad habit. WWW: http://search.cpan.org/dist/Parse-HTTP-UserAgent/ Feature safe: yes
2011-11-12 17:45:51 +01:00
CATEGORIES= www perl5
MASTER_SITES= CPAN
- Update to 0.35 Changes: http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes
2012-05-15 04:04:47 +02:00
MASTER_SITE_SUBDIR= CPAN:BURAK
- Add p5-Parse-HTTP-UserAgent 0.32 Parse::HTTP::UserAgent implements a rules-based parser and tries to identify MSIE, FireFox, Opera, Safari & Chrome first. It then tries to identify Mozilla, Netscape, Robots and the rest will be tried with a generic parser. There is also a structure dumper, useful for debugging. User agent strings are a complete mess since there is no standard format for them. They can be in various formats and can include more or less information depending on the vendor's (or the user's) choice. Also, it is not dependable since it is some arbitrary identification string. Any user agent can fake another. So, why deal with such a useless mess? You may want to see the choice of your visitors and can get some reliable data (even if some are fake) and generate some nice charts out of them or just want to send an HttpOnly cookie if the user agent seems to support it (and send a normal one if this is not the case). However, browser sniffing for client-side coding is considered a bad habit. WWW: http://search.cpan.org/dist/Parse-HTTP-UserAgent/ Feature safe: yes
2011-11-12 17:45:51 +01:00
PKGNAMEPREFIX= p5-
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Parser for the User Agent string
- Update to 0.38 - Add LICENSE Changes: http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes
2013-09-16 17:11:56 +02:00
LICENSE= ART10 GPLv1
LICENSE_COMB= dual
- Update to 0.34 - Add TEST_DEPENDS Changes: http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes Feature safe: yes
2012-04-09 19:43:00 +02:00
TEST_DEPENDS= p5-Test-Pod>=0:${PORTSDIR}/devel/p5-Test-Pod \
p5-Test-Pod-Coverage>=0:${PORTSDIR}/devel/p5-Test-Pod-Coverage
- Add PORTSCOUT: reject developer releases
2014-02-28 00:16:02 +01:00
PORTSCOUT= limit:[^_]*
- Convert to new perl framework
2013-08-21 16:08:06 +02:00
USE_PERL5= configure
USES= perl5
- Add p5-Parse-HTTP-UserAgent 0.32 Parse::HTTP::UserAgent implements a rules-based parser and tries to identify MSIE, FireFox, Opera, Safari & Chrome first. It then tries to identify Mozilla, Netscape, Robots and the rest will be tried with a generic parser. There is also a structure dumper, useful for debugging. User agent strings are a complete mess since there is no standard format for them. They can be in various formats and can include more or less information depending on the vendor's (or the user's) choice. Also, it is not dependable since it is some arbitrary identification string. Any user agent can fake another. So, why deal with such a useless mess? You may want to see the choice of your visitors and can get some reliable data (even if some are fake) and generate some nice charts out of them or just want to send an HttpOnly cookie if the user agent seems to support it (and send a normal one if this is not the case). However, browser sniffing for client-side coding is considered a bad habit. WWW: http://search.cpan.org/dist/Parse-HTTP-UserAgent/ Feature safe: yes
2011-11-12 17:45:51 +01:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink