Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Add lua, nodejs, octave, qore, and tk-specific variables. (tk and tk85
define the same variable, so I only included tk.) This relates to
PR pkg/56301, where I noticed various REPLACE_* variables were not
listed in Appendix E of the pkgsrc guide.
There is a separate issue related to Appendix E here. If wip/mk is
found, the auto-generation of the help topic list for the pkgsrc guide
includes anything it finds under that path, but that's potentially
misleading, and causes the generated list to see-saw back and forth as
committers do or do not have wip visible (I do not).
|
|
Seen in mk/fetch/fetch.mk for FETCH_USE_IPV4_ONLY.
|
|
|
|
|
|
|
|
The word "ignore" was too unspecific. There are lines that should be
printed, and there are lines that should be evaluated.
|
|
|
|
|
|
Before, searching for topic=socket did not find the documentation.
The detection of useful help topics is still not perfect since it now
finds sections that consist of a single word, such as the word
"undo-replace" in mk/install/replace.mk, but that will be fixed later,
after adding a few unit tests.
|
|
now.
|
|
|
|
GNU Awk on Cygwin warns about these.
|
|
These are reserved for the pkgsrc infrastructure.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The variable names are typically mentioned in one of these styles:
# Package-settable variables:
#
# VARNAME
# Description
# Package-settable variables:
#
# VARNAME
# Description
Lines that are indented with two tabs contain text. And if one of these
lines starts with a variable name, it is just a coincidence. A practical
example of this happening is in mk/misc/developer.mk 1.24, where PKGNAME
starts a line of description.
|
|
The check for target(help) prevents a warning when "make help" is run from
a category directory.
|
|
The index is sorted alphabetically and mentioned in a plain "make help"
call.
|
|
|
|
|
|
PKG_VERBOSE.
PKG_VERBOSE currently is mostly used consistently in order to pass the `-v'
option to various commands (FETCH_CMD, PATCH, plist/doc-compress,
pkg_delete(1)).
It is also used internally (and a bit less consistently) in other cases to
provide more information mostly useful only for debugging.
ok <bsiegert>
|
|
|
|
|
|
look for print/texlive/*.mk files for help.
Now documentation regarding TeX packages for pkgsrc MAINTAINERs and
developers is easily accessible via the "help" target.
ok wiz@
|
|
|
|
|
|
|
|
|
|
package creation.
There are very few things in pkgsrc that needs more than one hour per
process on decently fast hardware, so setting that as (soft) limit for
bulk builds avoids the infinite loops seen in some other packages. There
are a few select exceptions, i.e. flightgear-data needs more than one
hour for pkg_create when using xz. This flag allows selectively giving
those places more time without wasting resources in the broken cases.
|
|
|
|
discussion on tech-pkg.
BROKEN_ON_PLATFORM and NOT_FOR_PLATFORM are the same, except that
(now) BROKEN_ON_PLATFORM sets PKG_FAIL_REASON and NOT_FOR_PLATFORM
sets PKG_SKIP_REASON. BROKEN_EXCEPT_FOR_PLATFORM and ONLY_FOR_PLATFORM
correspond in the same way.
The idea is that going forward we will distinguish unbuildable
packages that theoretically ought to be fixed (these are BROKEN) from
packages where it doesn't make sense to build (these are NOT_FOR)...
examples of the former include most non-64-bit-clean packges; examples
of the latter include OS-specific language bindings.
A general review of the uses of NOT_FOR_PLATFORM and ONLY_FOR_PLATFORM
(converting many of them to BROKEN...) is coming up.
Similarly, a general review of the uses of PKG_FAIL_REASON and
PKG_SKIP_REASON is coming up.
For this to become useful, pbulk needs to be taught to report failing
and skipped packages differently - the idea is that failing packages
should be reported up front and skipped packages don't need to be. This
has not been done yet, but one set of things at a time...
|
|
|
|
like _PKG_VARS. Since there exists documentation on these internal
variables, it should be found by "bmake help".
|
|
|
|
Keep "none" a default value for PKG_DESTDIR_SUPPORT for now.
|
|
|
|
target that defaults to either stage-install or package-install,
depending on whether DESTDIR support is active and supported by the
package or not.
|
|
mk/defaults/mk.conf. I don't know when I removed it accidentally.
|
|
|
|
|
|
|
|
|
|
META_PACKAGE must be set before including bsd.prefs.mk.
|
|
|