blob: ddf33a9c9846c2201702221db5fe3ddfcc2ff66d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
$NetBSD: TODO,v 1.47 2006/06/03 00:12:38 rillig Exp $
Please add your own entries at the bottom of this file. If possible,
include the name of an example package where a warning should occur.
* fix false positive warnings
* ONLY_FOR_PLATFORM => NOT_FOR_PLATFORM
* -Wl,-rpath
* include "../../mk/bsd.prefs.mk" before using "+=".
* include "../../mk/bsd.prefs.mk" before any .if
* warn about the use of ${SED} in {pre,do,post}-install
* check for direct use of user names and group names
* Find a reliable, secure way to delete all CVS directories inside
${WRKSRC}. When that is finished, add a warning that using ${XARGS}
is insecure.
* detect spelling errors (like CONFLICT => CONFLICTS)
* warn about the use of ${WRKDIR:=...}, as this construct should only
be used with lists.
* mention the SUBST framework whenever ${SED} is used.
* check that Index: entries match the rest of the patch
* record with each substring its source location to be able to make
even more precise diagnostics
* check wether CONFIG* override match, e.g. CONFIGURE_DIRS most likely
needs matching CNOFIG_GUESS_OVERRIDE and CONFIG_SUB_OVERRIDE as well
* warn about BUILD_USES_MSGFMT and related defines being used when
devel/gettext-lib/buildlink3.mk is not explicitly included?
* Many of the checking routines need some context to provide better
warnings. For example, checkline_foo() may need to know what has
happened in the file before that line.
* Add checks for binary packages. See Debian/lintian for ideas.
* Check that USE_LIBTOOL=yes, when the PLIST contains *.la.
* Of the user-defined variables, some may be used at load-time and some
don't. Find out how pkglint can distinguish them.
|
