Annotation of wikisrc/pkgsrc/frequently_asked_questions_from_pkgsrc_developers.mdwn, revision 1.2
1.2 ! schmonz 1: **Contents**
! 2:
! 3: [[!toc levels=2]]
! 4:
! 5: # Questions & Answers
! 6:
! 7: ## How can I get a list of all [[basics/make]] variables that are used by pkgsrc?
! 8:
! 9:
! 10: That's difficult. But you can get a very good approximation by changing to a package directory and running the following command:
! 11:
! 12:
! 13: make -dv show-var VARNAME=VARNAME \
! 14: | sed -n 's,^Global:\([^ ]*\) =.*,\1,p' \
! 15: | sed 's,\..*,.*,' \
! 16: | sort -u \
! 17: | grep ^\[A-Z\] \
! 18: | less
! 19:
! 20:
! 21: Another possibility is to run bmake show-all. This will list many (but not all) variables.
! 22:
! 23: If you need more information about a specific variable, run bmake help topic=_VARNAME_ or have a look at [pkglint's variable definition file](http://cvsweb.de.netbsd.org/cgi-bin/cvsweb.cgi/pkgsrc/pkgtools/pkglint/files/makevars.map?rev=HEAD)
! 24:
! 25:
! 26: ## When patching a GNU-style configure script, where should I add changes?
! 27:
! 28: If you want your changes to override everything else, then look for "ac_config_files=" and put it somewhere before that line.
! 29:
! 30: ## I'm going to make incompatible changes to pkgsrc. Where should I document it?
! 31:
! 32: In the file doc/CHANGES-*.
! 33:
! 34: ## What's the difference between ${TEST}, test and [?
! 35:
! 36: There is practically no difference. All the standard options are supported on all platforms. See also [[pkgsrc/The pkgsrc portability guide#test]].
! 37:
! 38: # See also
! 39:
! 40: * [http://www.netbsd.org/Documentation/pkgsrc/devfaq.html](http://www.netbsd.org/Documentation/pkgsrc/devfaq.html)
! 41:
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb