kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/kyua-cli/Makefile

53 lines
1.3 KiB
Makefile
Raw Normal View History

Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
# $NetBSD: Makefile,v 1.6 2012/06/07 01:13:58 jmmv Exp $
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
#
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
DISTNAME= kyua-cli-0.4
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
CATEGORIES= devel
MASTER_SITES= http://kyua.googlecode.com/files/
MAINTAINER= jmmv@NetBSD.org
HOMEPAGE= http://code.google.com/p/kyua/
COMMENT= Kyua (automated testing framework) - Command line interface
LICENSE= 2-clause-bsd
PKG_DESTDIR_SUPPORT= user-destdir
GNU_CONFIGURE= yes
INFO_FILES= yes
MAKE_JOBS_SAFE= yes
USE_LANGUAGES= c++
USE_TOOLS= makeinfo pkg-config
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
PKG_OPTIONS_VAR= PKG_OPTIONS.kyua-cli
PKG_SUPPORTED_OPTIONS= tests
PKG_SUGGESTED_OPTIONS= tests
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
CONFIGURE_ARGS+= KYUA_CONFSUBDIR=
CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
CONFIGURE_ARGS+= --without-doxygen
PKG_SYSCONFSUBDIR= kyua
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
.include "../../mk/bsd.options.mk"
.if $(PKG_OPTIONS:Mtests)
CONFIGURE_ARGS+= --with-atf
PLIST_SUBST+= TESTS=
BUILDLINK_API_DEPENDS.atf+= atf>=0.15
. include "../../devel/atf/buildlink3.mk"
.else
CONFIGURE_ARGS+= --without-atf
PLIST_SUBST+= TESTS=@comment
.endif
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
post-install:
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
${INSTALL_DATA_DIR} ${DESTDIR}${PREFIX}/tests
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
${INSTALL_DATA} ${WRKSRC}/examples/Kyuafile.top \
${DESTDIR}${PREFIX}/tests/Kyuafile
Update kyua-cli to 0.3: Experimental version released on February 24th, 2012. * Made the 'test' command record the results of the executed test cases into a SQLite database. As a side effect, 'test' now supports a '--store' option to indicate where the database lives. * Added the 'report' command to generate plain-text reports of the test results stored in the database. The interface of this command is certainly subject to change at this point. * Added the 'db-exec' command to directly interact with the store database. * Issue 28: Added support for the 'require.memory' test case property introduced in ATF 0.15. * Renamed the user-specific configuration file from ~/.kyuarc to ~/.kyua/kyua.conf for consistency with other files stored in the ~/.kyua/ subdirectory. * Switched to use Lutok instead of our own wrappers over the Lua C library. Lutok is just what used to be our own utils::lua module, but is now distributed separately. * Removed the 'Atffile's from the source tree. Kyua is stable enough to generate trustworthy reports, and we do not want to give the impression that atf-run / atf-report are still supported. * Enabled logging to stderr for our own test programs. This makes it slightly easier to debug problems in our own code when we get a failing test.
2012-02-24 22:07:41 +01:00
.include "../../databases/sqlite3/buildlink3.mk"
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
BUILDLINK_API_DEPENDS.lutok+= lutok>=0.2
Update kyua-cli to 0.3: Experimental version released on February 24th, 2012. * Made the 'test' command record the results of the executed test cases into a SQLite database. As a side effect, 'test' now supports a '--store' option to indicate where the database lives. * Added the 'report' command to generate plain-text reports of the test results stored in the database. The interface of this command is certainly subject to change at this point. * Added the 'db-exec' command to directly interact with the store database. * Issue 28: Added support for the 'require.memory' test case property introduced in ATF 0.15. * Renamed the user-specific configuration file from ~/.kyuarc to ~/.kyua/kyua.conf for consistency with other files stored in the ~/.kyua/ subdirectory. * Switched to use Lutok instead of our own wrappers over the Lua C library. Lutok is just what used to be our own utils::lua module, but is now distributed separately. * Removed the 'Atffile's from the source tree. Kyua is stable enough to generate trustworthy reports, and we do not want to give the impression that atf-run / atf-report are still supported. * Enabled logging to stderr for our own test programs. This makes it slightly easier to debug problems in our own code when we get a failing test.
2012-02-24 22:07:41 +01:00
.include "../../devel/lutok/buildlink3.mk"
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
.include "../../lang/lua/buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink