kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/p5-Return-Value/Makefile

22 lines
630 B
Makefile
Raw Normal View History

Updating package for p5 module Return::Value from 1.302 to 1.666.001 Setting license to ${PERL5_LICENSE} Upstream changes: 1.666001 2009-06-08 1.666000 2009-06-08 formally declare Return::Value deprecated 1.303 2007-04-01 fix test to work on 5.5
2009-07-07 23:22:02 +02:00
# $NetBSD: Makefile,v 1.5 2009/07/07 21:22:02 sno Exp $
Polymorphic return values are really useful. Often, we just want to know if something worked or not. Other times, we'd like to know what the error text was. Still others, we may want to know what the error code was, and what the error properties were. We don't want to handle objects or data structures for every single return value, but we do want to check error conditions in our code because that's what good programmers do. When functions are successful they may return true, or perhaps some useful data. In the quest to provide consistent return values, this gets confusing between complex, informational errors and successful return values. This module provides these features with a simple API that should get you what you're looking for in each contex a return value is used in. Imported from pkgsrc-wip and packaged by kuli0020@umn.edu
2007-07-29 13:45:15 +02:00
Updating package for p5 module Return::Value from 1.302 to 1.666.001 Setting license to ${PERL5_LICENSE} Upstream changes: 1.666001 2009-06-08 1.666000 2009-06-08 formally declare Return::Value deprecated 1.303 2007-04-01 fix test to work on 5.5
2009-07-07 23:22:02 +02:00
DISTNAME= Return-Value-1.666001
PKGNAME= p5-${DISTNAME:S/666001/666.001/}
Polymorphic return values are really useful. Often, we just want to know if something worked or not. Other times, we'd like to know what the error text was. Still others, we may want to know what the error code was, and what the error properties were. We don't want to handle objects or data structures for every single return value, but we do want to check error conditions in our code because that's what good programmers do. When functions are successful they may return true, or perhaps some useful data. In the quest to provide consistent return values, this gets confusing between complex, informational errors and successful return values. This module provides these features with a simple API that should get you what you're looking for in each contex a return value is used in. Imported from pkgsrc-wip and packaged by kuli0020@umn.edu
2007-07-29 13:45:15 +02:00
CATEGORIES= devel perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=../by-authors/id/R/RJ/RJBS/}
Roman Kulik cannot maintain those packages anymore (he told me in private mail some months ago).
2008-07-20 18:09:34 +02:00
MAINTAINER= pkgsrc-users@NetBSD.org
Polymorphic return values are really useful. Often, we just want to know if something worked or not. Other times, we'd like to know what the error text was. Still others, we may want to know what the error code was, and what the error properties were. We don't want to handle objects or data structures for every single return value, but we do want to check error conditions in our code because that's what good programmers do. When functions are successful they may return true, or perhaps some useful data. In the quest to provide consistent return values, this gets confusing between complex, informational errors and successful return values. This module provides these features with a simple API that should get you what you're looking for in each contex a return value is used in. Imported from pkgsrc-wip and packaged by kuli0020@umn.edu
2007-07-29 13:45:15 +02:00
HOMEPAGE= http://search.cpan.org/dist/Return-Value/
COMMENT= Polymorphic Return Values
Updating package for p5 module Return::Value from 1.302 to 1.666.001 Setting license to ${PERL5_LICENSE} Upstream changes: 1.666001 2009-06-08 1.666000 2009-06-08 formally declare Return::Value deprecated 1.303 2007-04-01 fix test to work on 5.5
2009-07-07 23:22:02 +02:00
LICENSE= ${PERL5_LICENSE}
Polymorphic return values are really useful. Often, we just want to know if something worked or not. Other times, we'd like to know what the error text was. Still others, we may want to know what the error code was, and what the error properties were. We don't want to handle objects or data structures for every single return value, but we do want to check error conditions in our code because that's what good programmers do. When functions are successful they may return true, or perhaps some useful data. In the quest to provide consistent return values, this gets confusing between complex, informational errors and successful return values. This module provides these features with a simple API that should get you what you're looking for in each contex a return value is used in. Imported from pkgsrc-wip and packaged by kuli0020@umn.edu
2007-07-29 13:45:15 +02:00
Add DESTDIR support.
2008-06-12 04:14:13 +02:00
PKG_DESTDIR_SUPPORT= user-destdir
Polymorphic return values are really useful. Often, we just want to know if something worked or not. Other times, we'd like to know what the error text was. Still others, we may want to know what the error code was, and what the error properties were. We don't want to handle objects or data structures for every single return value, but we do want to check error conditions in our code because that's what good programmers do. When functions are successful they may return true, or perhaps some useful data. In the quest to provide consistent return values, this gets confusing between complex, informational errors and successful return values. This module provides these features with a simple API that should get you what you're looking for in each contex a return value is used in. Imported from pkgsrc-wip and packaged by kuli0020@umn.edu
2007-07-29 13:45:15 +02:00
DEPENDS+= {perl>=5.7.3,p5-Test-Simple>=0.47}:../../devel/p5-Test-Simple
USE_LANGUAGES= # empty
PERL5_PACKLIST= auto/Return/Value/.packlist
.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink