kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/devel/p5-Carp-Always-Color/Makefile

24 lines
517 B
Makefile
Raw Normal View History

- Update to 0.07 - Add LICENSE - Cleanup Makefile header - Remove outdated PERL_LEVEL check Changes: http://search.cpan.org/dist/Carp-Always-Color/Changes
2013-01-30 18:28:58 +01:00
# Created by: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>
- Add p5-Carp-Always-Color 0.05 Stack traces are hard to read when the messages wrap, because it's hard to tell when one message ends and the next message starts. Carp::Always::Color just colors the first line of each stacktrace, based on whether it's a warning or an error. If messages are being sent to a terminal, it colors them with terminal escape codes, otherwise it colors them with HTML (ideas for more intelligent behavior here are welcome). WWW: http://search.cpan.org/dist/Carp-Always-Color/
2011-09-20 10:54:11 +02:00
# $FreeBSD$
PORTNAME= Carp-Always-Color
- Update to 0.07 - Add LICENSE - Cleanup Makefile header - Remove outdated PERL_LEVEL check Changes: http://search.cpan.org/dist/Carp-Always-Color/Changes
2013-01-30 18:28:58 +01:00
PORTVERSION= 0.07
- Add p5-Carp-Always-Color 0.05 Stack traces are hard to read when the messages wrap, because it's hard to tell when one message ends and the next message starts. Carp::Always::Color just colors the first line of each stacktrace, based on whether it's a warning or an error. If messages are being sent to a terminal, it colors them with terminal escape codes, otherwise it colors them with HTML (ideas for more intelligent behavior here are welcome). WWW: http://search.cpan.org/dist/Carp-Always-Color/
2011-09-20 10:54:11 +02:00
CATEGORIES= devel perl5
MASTER_SITES= CPAN
PKGNAMEPREFIX= p5-
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Carp::Always, but with color
- Update to 0.07 - Add LICENSE - Cleanup Makefile header - Remove outdated PERL_LEVEL check Changes: http://search.cpan.org/dist/Carp-Always-Color/Changes
2013-01-30 18:28:58 +01:00
LICENSE= ART10 GPLv1
LICENSE_COMB= dual
- Add p5-Carp-Always-Color 0.05 Stack traces are hard to read when the messages wrap, because it's hard to tell when one message ends and the next message starts. Carp::Always::Color just colors the first line of each stacktrace, based on whether it's a warning or an error. If messages are being sent to a terminal, it colors them with terminal escape codes, otherwise it colors them with HTML (ideas for more intelligent behavior here are welcome). WWW: http://search.cpan.org/dist/Carp-Always-Color/
2011-09-20 10:54:11 +02:00
- Update to 0.07 - Add LICENSE - Cleanup Makefile header - Remove outdated PERL_LEVEL check Changes: http://search.cpan.org/dist/Carp-Always-Color/Changes
2013-01-30 18:28:58 +01:00
BUILD_DEPENDS= p5-Carp-Always>=0.10:${PORTSDIR}/devel/p5-Carp-Always
RUN_DEPENDS:= ${BUILD_DEPENDS}
- Update to 0.06 - Add TEST_DEPENDS Changes: http://search.cpan.org/dist/Carp-Always-Color/Changes Feature safe: yes
2012-03-12 03:39:21 +01:00
TEST_DEPENDS= p5-IO-Pty-Easy>=0:${PORTSDIR}/devel/p5-IO-Pty-Easy
- Convert to new perl framework
2013-08-21 16:08:06 +02:00
USE_PERL5= configure
USES= perl5
- Add p5-Carp-Always-Color 0.05 Stack traces are hard to read when the messages wrap, because it's hard to tell when one message ends and the next message starts. Carp::Always::Color just colors the first line of each stacktrace, based on whether it's a warning or an error. If messages are being sent to a terminal, it colors them with terminal escape codes, otherwise it colors them with HTML (ideas for more intelligent behavior here are welcome). WWW: http://search.cpan.org/dist/Carp-Always-Color/
2011-09-20 10:54:11 +02:00
- Update to 0.07 - Add LICENSE - Cleanup Makefile header - Remove outdated PERL_LEVEL check Changes: http://search.cpan.org/dist/Carp-Always-Color/Changes
2013-01-30 18:28:58 +01:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink