| @@ -1,14 +1,14 @@ | | | @@ -1,14 +1,14 @@ |
1 | $NetBSD: TODO,v 1.64 2008/03/06 09:34:41 rillig Exp $ | | 1 | $NetBSD: TODO,v 1.65 2008/03/10 22:01:04 tnn Exp $ |
2 | | | 2 | |
3 | Please add your own entries at the bottom of this file. If possible, | | 3 | Please add your own entries at the bottom of this file. If possible, |
4 | include the name of an example package where a warning should occur. | | 4 | include the name of an example package where a warning should occur. |
5 | | | 5 | |
6 | * fix false positive warnings | | 6 | * fix false positive warnings |
7 | * warn about the use of ${WRKDIR:=...}, as this construct should only | | 7 | * warn about the use of ${WRKDIR:=...}, as this construct should only |
8 | be used with lists. | | 8 | be used with lists. |
9 | * record with each substring its source location to be able to make | | 9 | * record with each substring its source location to be able to make |
10 | even more precise diagnostics | | 10 | even more precise diagnostics |
11 | * Many of the checking routines need some context to provide better | | 11 | * Many of the checking routines need some context to provide better |
12 | warnings. For example, checkline_foo() may need to know what has | | 12 | warnings. For example, checkline_foo() may need to know what has |
13 | happened in the file before that line. | | 13 | happened in the file before that line. |
14 | * Add checks for binary packages. See Debian/lintian for ideas. | | 14 | * Add checks for binary packages. See Debian/lintian for ideas. |
| @@ -35,13 +35,16 @@ include the name of an example package w | | | @@ -35,13 +35,16 @@ include the name of an example package w |
35 | | | 35 | |
36 | % | | 36 | % |
37 | | | 37 | |
38 | mail/mail-notification failed for Thomas, apparently because of an | | 38 | mail/mail-notification failed for Thomas, apparently because of an |
39 | unexpressed dependency on hicolor-icon-theme. I don't know if it's | | 39 | unexpressed dependency on hicolor-icon-theme. I don't know if it's |
40 | possible to add a way to notice that the PLIST contains hicolor files | | 40 | possible to add a way to notice that the PLIST contains hicolor files |
41 | but that there's no dependency, or perhaps a list of mappings of sets of | | 41 | but that there's no dependency, or perhaps a list of mappings of sets of |
42 | PLIST regexes to sets of required packages, or something. | | 42 | PLIST regexes to sets of required packages, or something. |
43 | | | 43 | |
44 | % | | 44 | % |
45 | | | 45 | |
46 | * don't complain about "procedure calls", like for pkg-build-options in | | 46 | * don't complain about "procedure calls", like for pkg-build-options in |
47 | the various buildlink3.mk files. | | 47 | the various buildlink3.mk files. |
| | | 48 | * To push DESTDIR support forward, it would be useful it pkglint warned |
| | | 49 | like this if PKG_DESTDIR_SUPPORT is not defined: |
| | | 50 | "WARN: Please consider adding DESTDIR support to the package." |