cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2795ba2341
openbsd-ports/databases/p5-DBD-Mock/Makefile

22 lines
378 B
Makefile
Raw Normal View History

Update to p5-DBD-Mock-1.58.
2020-11-06 03:12:13 -05:00
# $OpenBSD: Makefile,v 1.15 2020/11/06 08:12:13 benoit Exp $
import p5-DBD-Mock Testing with databases can be tricky. If you are developing a system married to a single database then you can make some assumptions about your environment and ask the user to provide relevant connection information. But if you need to test a framework that uses DBI, particularly a framework that uses different types of persistence schemes, then it may be more useful to simply verify what the framework is trying to do -- ensure the right SQL is generated and that the correct parameters are bound. DBD::Mock makes it easy to just modify your configuration (presumably held outside your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework. ok sthen@
2007-11-22 14:43:34 -05:00
Update to p5-DBD-Mock-1.55. from wen heping, afresh1@ and updated
2020-02-20 03:41:26 -05:00
COMMENT = mock database driver for testing
import p5-DBD-Mock Testing with databases can be tricky. If you are developing a system married to a single database then you can make some assumptions about your environment and ask the user to provide relevant connection information. But if you need to test a framework that uses DBI, particularly a framework that uses different types of persistence schemes, then it may be more useful to simply verify what the framework is trying to do -- ensure the right SQL is generated and that the correct parameters are bound. DBD::Mock makes it easy to just modify your configuration (presumably held outside your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework. ok sthen@
2007-11-22 14:43:34 -05:00
Update to p5-DBD-Mock-1.55. from wen heping, afresh1@ and updated
2020-02-20 03:41:26 -05:00
MODULES = cpan
PKG_ARCH = *
Update to p5-DBD-Mock-1.58.
2020-11-06 03:12:13 -05:00
DISTNAME = DBD-Mock-1.58
Update to p5-DBD-Mock-1.55. from wen heping, afresh1@ and updated
2020-02-20 03:41:26 -05:00
CATEGORIES = databases devel
import p5-DBD-Mock Testing with databases can be tricky. If you are developing a system married to a single database then you can make some assumptions about your environment and ask the user to provide relevant connection information. But if you need to test a framework that uses DBI, particularly a framework that uses different types of persistence schemes, then it may be more useful to simply verify what the framework is trying to do -- ensure the right SQL is generated and that the correct parameters are bound. DBD::Mock makes it easy to just modify your configuration (presumably held outside your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework. ok sthen@
2007-11-22 14:43:34 -05:00
# Perl
replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes
2019-07-12 16:43:27 -04:00
PERMIT_PACKAGE= Yes
import p5-DBD-Mock Testing with databases can be tricky. If you are developing a system married to a single database then you can make some assumptions about your environment and ask the user to provide relevant connection information. But if you need to test a framework that uses DBI, particularly a framework that uses different types of persistence schemes, then it may be more useful to simply verify what the framework is trying to do -- ensure the right SQL is generated and that the correct parameters are bound. DBD::Mock makes it easy to just modify your configuration (presumably held outside your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework. ok sthen@
2007-11-22 14:43:34 -05:00
Update to p5-DBD-Mock-1.55. from wen heping, afresh1@ and updated
2020-02-20 03:41:26 -05:00
RUN_DEPENDS = databases/p5-DBI>=1.3
import p5-DBD-Mock Testing with databases can be tricky. If you are developing a system married to a single database then you can make some assumptions about your environment and ask the user to provide relevant connection information. But if you need to test a framework that uses DBI, particularly a framework that uses different types of persistence schemes, then it may be more useful to simply verify what the framework is trying to do -- ensure the right SQL is generated and that the correct parameters are bound. DBD::Mock makes it easy to just modify your configuration (presumably held outside your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework. ok sthen@
2007-11-22 14:43:34 -05:00
Update to p5-DBD-Mock-1.55. from wen heping, afresh1@ and updated
2020-02-20 03:41:26 -05:00
TEST_DEPENDS = devel/p5-Test-Exception>=0.31
import p5-DBD-Mock Testing with databases can be tricky. If you are developing a system married to a single database then you can make some assumptions about your environment and ask the user to provide relevant connection information. But if you need to test a framework that uses DBI, particularly a framework that uses different types of persistence schemes, then it may be more useful to simply verify what the framework is trying to do -- ensure the right SQL is generated and that the correct parameters are bound. DBD::Mock makes it easy to just modify your configuration (presumably held outside your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework. ok sthen@
2007-11-22 14:43:34 -05:00
Update to p5-DBD-Mock-1.55. from wen heping, afresh1@ and updated
2020-02-20 03:41:26 -05:00
CONFIGURE_STYLE=modbuild tiny
MAKE_ENV += TEST_POD=1
import p5-DBD-Mock Testing with databases can be tricky. If you are developing a system married to a single database then you can make some assumptions about your environment and ask the user to provide relevant connection information. But if you need to test a framework that uses DBI, particularly a framework that uses different types of persistence schemes, then it may be more useful to simply verify what the framework is trying to do -- ensure the right SQL is generated and that the correct parameters are bound. DBD::Mock makes it easy to just modify your configuration (presumably held outside your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework. ok sthen@
2007-11-22 14:43:34 -05:00
.include <bsd.port.mk>
Reference in New Issue Copy Permalink