summaryrefslogtreecommitdiff
path: root/regress
AgeCommit message (Collapse)AuthorFilesLines
2019-03-24regress/buildlink-libtool: fix failing testrillig1-3/+3
The comment above that test was a copy-and-paste error. It got almost 15 years old.
2019-03-24regress/pkg-options: fix regression test for PKG_OPTIONS frameworkrillig4-5/+5
Just a few changes in the wording, which have been introduced in 2007.
2019-03-24mk/tools: correctly quote arguments in the tool wrapper logrillig3-46/+85
Before, the tool arguments were written to the log as plain strings. Now the arguments are properly quoted, which makes it possible to replay the commands by copying them from the .work.log file. This only affects tools that are shell builtins (echo, true, false), get additional arguments (mkdir -p) or define a custom TOOLS_SCRIPT (pkg-config, to set an environment variable; or autotools). Tools that are symlinked to the real tool are not affected. The calls to the compiler are already properly logged since cwrappers takes care of that. This commit therefore makes the log entries for the compilers and the other tools more similar.
2019-03-24mk/tools: fix quoting when logging tool invocationsrillig2-12/+49
When a package or the infrastructure defined a tool with custom TOOLS_ARGS or TOOLS_SCRIPT containing special characters, these could lead to unintuitive interactions at the time when that tool invocation was logged in the tool wrapper log. Some of the logging output ended up on stdout, while some of the normal output ended up in the log, and parts of the quoted arguments were even evaluated as shell commands. The logging of the wrapped tool commands is not perfect yet, but at least it's much more predictable now.
2019-03-23regress/tools: show that TOOLS_SCRIPT is not always logged properlyrillig3-42/+118
2019-03-22regress/tools: demonstrate wrong shell quoting in the tools wrapperrillig2-2/+33
2019-03-22mk/tools: fix unintended filename expansion in the tool wrapper log filerillig1-8/+33
2019-03-22regress/tools: demonstrate wrong quoting in tools wrapper loggingrillig3-8/+48
2019-03-21regress/infra-unittests: add small framework for testing mk/ with mocksrillig5-1/+239
2019-03-17regress/compiler: fix regression testrillig2-7/+5
2019-03-17mk/subst.mk: substitute embedded newlines, escape dots in variable namesrillig2-8/+11
2019-03-17regress/subst: demonstrate that SUBST_VARS doesn't pass newlinesrillig4-13/+61
Sure, it's an edge case and has not been necessary until now. Nevertheless it's good to see how this can be done. Variables having dots in their names are also not handled completely correct. This also didn't occur in practice since the variable names passed to SUBST_VARS are usually A-Za-z0-9_ only.
2019-03-17regress/subst: enable regression testrillig2-3/+11
2018-12-05regress/tools: clarify that only the NetBSD 7 shell exhibits this bugrillig1-4/+4
The test has been changed again to fail since making the test pass would mean this bug could later silently show up inside a large GNU configure script where it would be impossible to find. Therefore, when using pkgsrc on NetBSD 7, it is better to switch to another shell for doing pkgsrc work. The comment has been updated to be more accurate.
2018-11-30regress/tools: disable failing test on NetBSDrillig1-1/+4
See bin/53754.
2018-11-30regress/show-all: fix regression test after infrastructure changerillig1-1/+3
2018-11-30regress/make-quoting: adjust to bmake change from 2015rillig3-10/+11
2018-11-11mk/misc: adjust layout of the show-all output to pkgsrc formatrillig2-34/+34
In Makefiles, the variable values are aligned vertically. This format is now also used in the show-all target, which makes it easier readable. Some more variables have been marked as multi-value, and single-valued variables ending in space are clearly marked. Without the latter, the regression test would have a line with significant trailing whitespace.
2018-11-10mk/misc: in show-all, list values of *_ENV and *_ARGS in separate linesrillig5-1/+114
The *_ENV and *_ARG values are typically very long, and reading them in a single line is unnecessarily difficult. Therefore, each of their values is listed on a separate line, for example: fetch: usr DIST_PATH (undefined) pkg MASTER_SITES = \ http://ftp.gnome.org/pub/GNOME/sources/glib/2.56/ \ ftp://ftp.gnome.org/pub/GNOME/sources/glib/2.56/ \ ftp://ftp.cse.buffalo.edu/pub/Gnome/sources/glib/2.56/ \ https://download.gnome.org/sources/glib/2.56/ \ # end of MASTER_SITES pkg DIST_SUBDIR (undefined)
2018-11-09regress/env-vars: make test output more conciserillig4-18/+18
2018-11-09regress: Add a link to the pkgsrc guiderillig1-2/+3
2018-11-09regress: add env-varsrillig1-1/+4
2018-11-09regress/env-vars: demonstrate where and how the *_ENV variables are setrillig6-0/+129
2018-08-22Recursive bump for perl5-5.28.0wiz1-2/+2
2016-06-11Fixed pkglint warnings.rillig2-3/+6
2016-06-11Added regression test for portability checks.rillig5-1/+57
2016-04-11update PKG_{FAIL,SKIP}_REASON with +=dbj1-2/+2
2015-06-12Recursive PKGREVISION bump for all packages mentioning 'perl',wiz1-2/+2
having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
2015-06-07Sync spec with reality.joerg1-3/+1
2015-06-07Support DESTDIR, drop @dirrm. Give a working WRKSRC.joerg1-6/+5
2015-03-06Package has no distfiles, which is expected.tnn1-1/+2
2014-06-21Do not use a naked "make", instead use TEST_MAKE. Now it fails differently.bsiegert1-2/+2
2014-06-21Add PLISTs for all regression tests. The infrastructure now setsbsiegert13-0/+0
PKG_FAIL_REASON if there is no PLIST, breaking all but one test. Goes from "1 passed, 12 failed" to "6 passed, 7 failed" on Mac OS. "haha" schmonz@
2014-05-29Bump for perl-5.20.0.wiz1-1/+2
Do it for all packages that * mention perl, or * have a directory name starting with p5-*, or * depend on a package starting with p5- like last time, for 5.18, where this didn't lead to complaints. Let me know if you have any this time.
2010-03-21Reset maintainer, developer lost his commit bit.wiz4-8/+8
2009-06-14Remove @dirrm entries from PLISTsjoerg1-2/+1
2009-04-09Remove redundant EXTRACT_ONLY and NO_CHECKSUM declarations.joerg10-26/+10
Retire NO_PACAKGE as there is no technical reason for it.
2009-04-08Remove the remaining NO_MTREE definitions, it has been a nop for ajoerg1-2/+1
while.
2009-03-21Fix MAINTAINER.darcy1-2/+2
2008-04-30Drop maintainershipjmmv1-2/+2
Stop lying and drop maintainership of these packages. I have not maintained them for a very long time already, so leave room for fresh blood to take over them.
2008-03-04Resign from maintaining a lot of packages, so everyone is free to updaterillig6-12/+12
them at will.
2007-09-25Back out previous. Pointed out by uebayasi@ and martti@.hira1-2/+2
2007-09-25ln -> ${LN}.hira1-2/+2
2007-09-09Added a testcase for tar.rillig2-3/+27
2007-08-13Added mk/misc/category.mk, which contains the definitions that are onlyrillig1-2/+2
useful for category Makefiles, as opposed to bsd.pkg.subdir.mk, which is also relevant for the top-level directory. Adjusted the category Makefiles.
2007-07-12Add some regression tests for backing up existing files, e.g. "-b" andjlam1-1/+38
"-B fmt".
2007-07-04Add a test to verify that nonexistent intermediate directories arejlam1-2/+29
created with the proper permissions. XXX sysutils/install-sh isn't quite right the same as /usr/bin/install XXX because it ignores the umask for directory creation.
2007-06-20Test the install-sh script from sysutils/install-sh instead of the localjlam2-290/+12
one (which has actually migrated to sysutils/install-sh as of 20070620).
2007-03-08Added a testcase for offsetof. Reorganized the rest.rillig6-18/+54
2007-03-07Added a regression test for the SUBST framework, especially the newlyrillig3-1/+38
introduced SUBST_VARS.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-16 20:46:18 +0000