pkgsrc/pkgtools/pkglint/PLIST

145 lines
6.3 KiB
Text
Raw Normal View History

@comment $NetBSD: PLIST,v 1.27 2020/06/14 11:35:54 rillig Exp $
bin/pkglint
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint.a
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint/getopt.a
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint/histogram.a
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint/intqa.a
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint/licenses.a
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint/makepat.a
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint/pkgver.a
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint/regex.a
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint/textproc.a
gopkg/pkg/${GO_PLATFORM}/netbsd.org/pkglint/trace.a
gopkg/src/netbsd.org/pkglint/alternatives.go
gopkg/src/netbsd.org/pkglint/alternatives_test.go
gopkg/src/netbsd.org/pkglint/autofix.go
gopkg/src/netbsd.org/pkglint/autofix_test.go
gopkg/src/netbsd.org/pkglint/buildlink3.go
gopkg/src/netbsd.org/pkglint/buildlink3_test.go
gopkg/src/netbsd.org/pkglint/category.go
gopkg/src/netbsd.org/pkglint/category_test.go
gopkg/src/netbsd.org/pkglint/check_test.go
pkgtools/pkglint: update to 5.6.12 Changes since 5.6.11: * In buildlink3.mk files, print the paths relative to the line, not to the pkgsrc root. * When explaining that a variable cannot be set/used because of wrong permissions, list the permissions. This provides more transparency than just stating that the desired action is not allowed. * When pkglint checks a pkgsrc-wip package, don't warn about malformed lines in doc/CHANGES-* since pkgsrc-wip users typically cannot do anything about these errors. * In profiling mode, not only the code coverage and the performance statistics are dumped, the whole heap is also dumped to see which parts of pkglint consume the most heap memory. Pkglint now needs less heap memory than before, which mainly affects full scans. * The checks for absolute pathnames have gone. They were of questionable value since pkglint has failed to give proper advice on how to fix them properly, at least for the last 12 years. * The check that pkgsrc-wip packages should only use exact CVS Ids (the unexpanded variant) has been disabled again. It occurred about 16000 times but even fixing it wouldn't improve anything since it was mostly a formatting issue without any practical consequences. * Warn about trailing variable modifiers like in ${VAR:S,from,to,extra}. * Properly parse ${VAR:!command!}. * Suggest to replace SUBST_SED with SUBST_VARS where possible, even with complicated shell quoting. Pkglint can autofix most of these overly verbose cases. * Load builtin.mk whenever the corresponding buildlink3.mk file is included. This fixes several warnings about undefined variables (especially for packages using OpenSSL). * Parse .for lines like bmake does since 2015, splitting words like in brk_string. * Optionally show a warning even if it cannot be autofixed by pkglint. This is useful for the SUBST_VARS replacement since even when pkglint cannot automatically replace the code, there are still cases where it can warn at least. * As always, several refactorings.
2019-01-26 17:31:33 +01:00
gopkg/src/netbsd.org/pkglint/cmd/pkglint/main.go
gopkg/src/netbsd.org/pkglint/cmd/pkglint/main_test.go
gopkg/src/netbsd.org/pkglint/distinfo.go
gopkg/src/netbsd.org/pkglint/distinfo_test.go
gopkg/src/netbsd.org/pkglint/files.go
gopkg/src/netbsd.org/pkglint/files_test.go
gopkg/src/netbsd.org/pkglint/fuzzer_test.go
gopkg/src/netbsd.org/pkglint/getopt/getopt.go
gopkg/src/netbsd.org/pkglint/getopt/getopt_test.go
gopkg/src/netbsd.org/pkglint/histogram/histogram.go
gopkg/src/netbsd.org/pkglint/histogram/histogram_test.go
gopkg/src/netbsd.org/pkglint/homepage.go
gopkg/src/netbsd.org/pkglint/homepage_test.go
gopkg/src/netbsd.org/pkglint/intqa/qa.go
gopkg/src/netbsd.org/pkglint/intqa/qa_test.go
gopkg/src/netbsd.org/pkglint/licenses.go
gopkg/src/netbsd.org/pkglint/licenses/licenses.go
gopkg/src/netbsd.org/pkglint/licenses/licenses.y
gopkg/src/netbsd.org/pkglint/licenses/licenses_test.go
gopkg/src/netbsd.org/pkglint/licenses/licensesyacc.go
gopkg/src/netbsd.org/pkglint/licenses/licensesyacc.log
gopkg/src/netbsd.org/pkglint/licenses_test.go
gopkg/src/netbsd.org/pkglint/line.go
gopkg/src/netbsd.org/pkglint/line_test.go
gopkg/src/netbsd.org/pkglint/linechecker.go
gopkg/src/netbsd.org/pkglint/linechecker_test.go
gopkg/src/netbsd.org/pkglint/lines.go
gopkg/src/netbsd.org/pkglint/lines_test.go
pkgtools/pkglint: update to 19.3.14 Changes since 19.3.13: When pkglint suggests to replace !empty(VARNAME:Mfixed) with ${VARNAME} == fixed, the exact suggested expression is now part of the diagnostic. The check and the autofix have been improved. They now apply only to the last modifier in the whole chain, everything else was a bug in pkglint. Pkglint now knows the scope of variables better than before. It knows the difference between variables from <sys.mk> like MACHINE_ARCH, which are always in scope, and those from mk/defaults/mk.conf, which only come into scope later, after bsd.prefs.mk has been included. It warns when variables are used too early, for example in .if conditions. The pathnames in ALTERNATIVES files are now checked for absolute pathnames. This mistake doesn't happen in practice, but the code for converting the different path types internally made it necessary to add these checks. At least this prevents typos. The special check for obsolete licenses has been removed since their license files have been removed and that is checked as well. Variables named *_AWK may be appended to. The variables _PKG_SILENT and _PKG_DEBUG are no longer deprecated, they are obsolete now. They are not used in main pkgsrc and pkgsrc-wip anymore. When a package sets a default value for a user-settable variable (which is something that should not happen anyway), it should .include bsd.prefs.mk before, in order to not accidentally overwrite the user-specified value. Variable modifiers of the form :from=to are now parsed like in bmake. They are greedy and eat up any following colons as well. This means that ${VAR:.c=.o:Q} replaces source.c with source.o:Q, instead of quoting it. Pkglint now warns about such cases. The handling of relative paths in diagnostics is now consistent. All paths that are part of a diagnostic are relative to the line that issues the diagnostic. Fatal errors are no longer suppressed in --autofix mode. Plus lots of refactoring, to prevent accidental mixing of incompatible relative paths.
2019-12-08 01:06:37 +01:00
gopkg/src/netbsd.org/pkglint/lineslexer.go
gopkg/src/netbsd.org/pkglint/lineslexer_test.go
gopkg/src/netbsd.org/pkglint/logging.go
gopkg/src/netbsd.org/pkglint/logging_test.go
gopkg/src/netbsd.org/pkglint/makepat/pat.go
gopkg/src/netbsd.org/pkglint/makepat/pat_test.go
pkgtools/pkglint: update to 19.3.14 Changes since 19.3.13: When pkglint suggests to replace !empty(VARNAME:Mfixed) with ${VARNAME} == fixed, the exact suggested expression is now part of the diagnostic. The check and the autofix have been improved. They now apply only to the last modifier in the whole chain, everything else was a bug in pkglint. Pkglint now knows the scope of variables better than before. It knows the difference between variables from <sys.mk> like MACHINE_ARCH, which are always in scope, and those from mk/defaults/mk.conf, which only come into scope later, after bsd.prefs.mk has been included. It warns when variables are used too early, for example in .if conditions. The pathnames in ALTERNATIVES files are now checked for absolute pathnames. This mistake doesn't happen in practice, but the code for converting the different path types internally made it necessary to add these checks. At least this prevents typos. The special check for obsolete licenses has been removed since their license files have been removed and that is checked as well. Variables named *_AWK may be appended to. The variables _PKG_SILENT and _PKG_DEBUG are no longer deprecated, they are obsolete now. They are not used in main pkgsrc and pkgsrc-wip anymore. When a package sets a default value for a user-settable variable (which is something that should not happen anyway), it should .include bsd.prefs.mk before, in order to not accidentally overwrite the user-specified value. Variable modifiers of the form :from=to are now parsed like in bmake. They are greedy and eat up any following colons as well. This means that ${VAR:.c=.o:Q} replaces source.c with source.o:Q, instead of quoting it. Pkglint now warns about such cases. The handling of relative paths in diagnostics is now consistent. All paths that are part of a diagnostic are relative to the line that issues the diagnostic. Fatal errors are no longer suppressed in --autofix mode. Plus lots of refactoring, to prevent accidental mixing of incompatible relative paths.
2019-12-08 01:06:37 +01:00
gopkg/src/netbsd.org/pkglint/mkassignchecker.go
gopkg/src/netbsd.org/pkglint/mkassignchecker_test.go
gopkg/src/netbsd.org/pkglint/mkcondchecker.go
gopkg/src/netbsd.org/pkglint/mkcondchecker_test.go
gopkg/src/netbsd.org/pkglint/mklexer.go
gopkg/src/netbsd.org/pkglint/mklexer_test.go
gopkg/src/netbsd.org/pkglint/mkline.go
gopkg/src/netbsd.org/pkglint/mkline_test.go
gopkg/src/netbsd.org/pkglint/mklinechecker.go
gopkg/src/netbsd.org/pkglint/mklinechecker_test.go
gopkg/src/netbsd.org/pkglint/mklineparser.go
gopkg/src/netbsd.org/pkglint/mklineparser_test.go
gopkg/src/netbsd.org/pkglint/mklines.go
gopkg/src/netbsd.org/pkglint/mklines_test.go
gopkg/src/netbsd.org/pkglint/mkparser.go
gopkg/src/netbsd.org/pkglint/mkparser_test.go
gopkg/src/netbsd.org/pkglint/mkshparser.go
gopkg/src/netbsd.org/pkglint/mkshparser_test.go
gopkg/src/netbsd.org/pkglint/mkshtypes.go
gopkg/src/netbsd.org/pkglint/mkshtypes_test.go
gopkg/src/netbsd.org/pkglint/mkshwalker.go
gopkg/src/netbsd.org/pkglint/mkshwalker_test.go
pkgtools/pkglint: update to 5.7.2 Changes since 5.7.1: * Fixed detection of GNU_CONFIGURE=yes combined with USE_LANGUAGES missing c. This combination tends to fail in the configure phase. * When the distinfo doesn't contain all hashes for the downloaded distfiles (typically SHA512 is missing) and the distfiles are actually downloaded to ${PKGSRCDIR}/distfiles, pkglint can now add the missing hashes. It only does this if there is at least one existing hash and if all existing hashes are correct. * The check for redundant variables has been improved considerably. Before there were several situations in which pkglint didn't get the redundant variable definitions right because its internal model only mimicked reality. The model has been improved and so have the diagnostics. * Pkglint only warns about wrong permissions (for defining or using a variable) when it knows the type of the variable and the permissions for the current file. Before, it had also warned if the permissions for the current file were not explicitly defined. * CFLAGS and LDFLAGS may be appended in buildlink3.mk files. This had been disallowed before, for no apparent reason. There are several places in pkgsrc where especially CFLAGS.${OPSYS} is appended to. * Cleaned up internal handling of relative paths. Previously pkglint sometimes resolved relative paths using the wrong base directory, which led to all kinds of wrong warnings and strange behavior. * Fixed lots of edge cases when parsing Makefile lines. These cases don't occur often but experience tells that the most fundamental code must be as correct as possible (see the handling of relative paths above). * Lots of refactoring and housekeeping, as always.
2019-03-10 20:01:50 +01:00
gopkg/src/netbsd.org/pkglint/mktokenslexer.go
gopkg/src/netbsd.org/pkglint/mktokenslexer_test.go
gopkg/src/netbsd.org/pkglint/mktypes.go
gopkg/src/netbsd.org/pkglint/mktypes_test.go
pkgtools/pkglint: update to 19.3.14 Changes since 19.3.13: When pkglint suggests to replace !empty(VARNAME:Mfixed) with ${VARNAME} == fixed, the exact suggested expression is now part of the diagnostic. The check and the autofix have been improved. They now apply only to the last modifier in the whole chain, everything else was a bug in pkglint. Pkglint now knows the scope of variables better than before. It knows the difference between variables from <sys.mk> like MACHINE_ARCH, which are always in scope, and those from mk/defaults/mk.conf, which only come into scope later, after bsd.prefs.mk has been included. It warns when variables are used too early, for example in .if conditions. The pathnames in ALTERNATIVES files are now checked for absolute pathnames. This mistake doesn't happen in practice, but the code for converting the different path types internally made it necessary to add these checks. At least this prevents typos. The special check for obsolete licenses has been removed since their license files have been removed and that is checked as well. Variables named *_AWK may be appended to. The variables _PKG_SILENT and _PKG_DEBUG are no longer deprecated, they are obsolete now. They are not used in main pkgsrc and pkgsrc-wip anymore. When a package sets a default value for a user-settable variable (which is something that should not happen anyway), it should .include bsd.prefs.mk before, in order to not accidentally overwrite the user-specified value. Variable modifiers of the form :from=to are now parsed like in bmake. They are greedy and eat up any following colons as well. This means that ${VAR:.c=.o:Q} replaces source.c with source.o:Q, instead of quoting it. Pkglint now warns about such cases. The handling of relative paths in diagnostics is now consistent. All paths that are part of a diagnostic are relative to the line that issues the diagnostic. Fatal errors are no longer suppressed in --autofix mode. Plus lots of refactoring, to prevent accidental mixing of incompatible relative paths.
2019-12-08 01:06:37 +01:00
gopkg/src/netbsd.org/pkglint/mkvarusechecker.go
gopkg/src/netbsd.org/pkglint/mkvarusechecker_test.go
gopkg/src/netbsd.org/pkglint/options.go
gopkg/src/netbsd.org/pkglint/options_test.go
gopkg/src/netbsd.org/pkglint/package.go
gopkg/src/netbsd.org/pkglint/package_test.go
gopkg/src/netbsd.org/pkglint/paragraph.go
gopkg/src/netbsd.org/pkglint/paragraph_test.go
gopkg/src/netbsd.org/pkglint/patches.go
gopkg/src/netbsd.org/pkglint/patches_test.go
gopkg/src/netbsd.org/pkglint/path.go
gopkg/src/netbsd.org/pkglint/path_test.go
gopkg/src/netbsd.org/pkglint/pkglint.0
gopkg/src/netbsd.org/pkglint/pkglint.1
gopkg/src/netbsd.org/pkglint/pkglint.go
gopkg/src/netbsd.org/pkglint/pkglint_test.go
gopkg/src/netbsd.org/pkglint/pkgsrc.go
gopkg/src/netbsd.org/pkglint/pkgsrc_test.go
gopkg/src/netbsd.org/pkglint/pkgver/vercmp.go
gopkg/src/netbsd.org/pkglint/pkgver/vercmp_test.go
gopkg/src/netbsd.org/pkglint/plist.go
gopkg/src/netbsd.org/pkglint/plist_test.go
pkgtools/pkglint: update to 5.7.2 Changes since 5.7.1: * Fixed detection of GNU_CONFIGURE=yes combined with USE_LANGUAGES missing c. This combination tends to fail in the configure phase. * When the distinfo doesn't contain all hashes for the downloaded distfiles (typically SHA512 is missing) and the distfiles are actually downloaded to ${PKGSRCDIR}/distfiles, pkglint can now add the missing hashes. It only does this if there is at least one existing hash and if all existing hashes are correct. * The check for redundant variables has been improved considerably. Before there were several situations in which pkglint didn't get the redundant variable definitions right because its internal model only mimicked reality. The model has been improved and so have the diagnostics. * Pkglint only warns about wrong permissions (for defining or using a variable) when it knows the type of the variable and the permissions for the current file. Before, it had also warned if the permissions for the current file were not explicitly defined. * CFLAGS and LDFLAGS may be appended in buildlink3.mk files. This had been disallowed before, for no apparent reason. There are several places in pkgsrc where especially CFLAGS.${OPSYS} is appended to. * Cleaned up internal handling of relative paths. Previously pkglint sometimes resolved relative paths using the wrong base directory, which led to all kinds of wrong warnings and strange behavior. * Fixed lots of edge cases when parsing Makefile lines. These cases don't occur often but experience tells that the most fundamental code must be as correct as possible (see the handling of relative paths above). * Lots of refactoring and housekeeping, as always.
2019-03-10 20:01:50 +01:00
gopkg/src/netbsd.org/pkglint/redundantscope.go
gopkg/src/netbsd.org/pkglint/redundantscope_test.go
gopkg/src/netbsd.org/pkglint/regex/regex.go
gopkg/src/netbsd.org/pkglint/scope.go
gopkg/src/netbsd.org/pkglint/scope_test.go
gopkg/src/netbsd.org/pkglint/shell.go
gopkg/src/netbsd.org/pkglint/shell.y
gopkg/src/netbsd.org/pkglint/shell_test.go
gopkg/src/netbsd.org/pkglint/shellyacc.go
gopkg/src/netbsd.org/pkglint/shellyacc.log
gopkg/src/netbsd.org/pkglint/shtokenizer.go
gopkg/src/netbsd.org/pkglint/shtokenizer_test.go
gopkg/src/netbsd.org/pkglint/shtypes.go
gopkg/src/netbsd.org/pkglint/shtypes_test.go
gopkg/src/netbsd.org/pkglint/substcontext.go
gopkg/src/netbsd.org/pkglint/substcontext_test.go
gopkg/src/netbsd.org/pkglint/textproc/lexer.go
gopkg/src/netbsd.org/pkglint/textproc/lexer_bench_test.go
gopkg/src/netbsd.org/pkglint/textproc/lexer_test.go
gopkg/src/netbsd.org/pkglint/tools.go
gopkg/src/netbsd.org/pkglint/tools_test.go
gopkg/src/netbsd.org/pkglint/toplevel.go
gopkg/src/netbsd.org/pkglint/toplevel_test.go
gopkg/src/netbsd.org/pkglint/trace/tracing.go
gopkg/src/netbsd.org/pkglint/trace/tracing_test.go
gopkg/src/netbsd.org/pkglint/util.go
gopkg/src/netbsd.org/pkglint/util_test.go
gopkg/src/netbsd.org/pkglint/var.go
gopkg/src/netbsd.org/pkglint/var_test.go
gopkg/src/netbsd.org/pkglint/varalignblock.go
gopkg/src/netbsd.org/pkglint/varalignblock_test.go
gopkg/src/netbsd.org/pkglint/vardefs.go
gopkg/src/netbsd.org/pkglint/vardefs_test.go
gopkg/src/netbsd.org/pkglint/vargroups.go
gopkg/src/netbsd.org/pkglint/vargroups_test.go
gopkg/src/netbsd.org/pkglint/vartype.go
gopkg/src/netbsd.org/pkglint/vartype_test.go
gopkg/src/netbsd.org/pkglint/vartypecheck.go
gopkg/src/netbsd.org/pkglint/vartypecheck_test.go
man/man1/pkglint.1
pkgtools/pkglint: update to 19.3.14 Changes since 19.3.13: When pkglint suggests to replace !empty(VARNAME:Mfixed) with ${VARNAME} == fixed, the exact suggested expression is now part of the diagnostic. The check and the autofix have been improved. They now apply only to the last modifier in the whole chain, everything else was a bug in pkglint. Pkglint now knows the scope of variables better than before. It knows the difference between variables from <sys.mk> like MACHINE_ARCH, which are always in scope, and those from mk/defaults/mk.conf, which only come into scope later, after bsd.prefs.mk has been included. It warns when variables are used too early, for example in .if conditions. The pathnames in ALTERNATIVES files are now checked for absolute pathnames. This mistake doesn't happen in practice, but the code for converting the different path types internally made it necessary to add these checks. At least this prevents typos. The special check for obsolete licenses has been removed since their license files have been removed and that is checked as well. Variables named *_AWK may be appended to. The variables _PKG_SILENT and _PKG_DEBUG are no longer deprecated, they are obsolete now. They are not used in main pkgsrc and pkgsrc-wip anymore. When a package sets a default value for a user-settable variable (which is something that should not happen anyway), it should .include bsd.prefs.mk before, in order to not accidentally overwrite the user-specified value. Variable modifiers of the form :from=to are now parsed like in bmake. They are greedy and eat up any following colons as well. This means that ${VAR:.c=.o:Q} replaces source.c with source.o:Q, instead of quoting it. Pkglint now warns about such cases. The handling of relative paths in diagnostics is now consistent. All paths that are part of a diagnostic are relative to the line that issues the diagnostic. Fatal errors are no longer suppressed in --autofix mode. Plus lots of refactoring, to prevent accidental mixing of incompatible relative paths.
2019-12-08 01:06:37 +01:00
@pkgdir man/cat1