| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
details.
|
|
of packages when it is already defined by the user.
|
|
|
|
other libraries (specified with -l).
Fixes a linking problem in net-snmp, where the Perl DynaLoader.a library
becomes out-of-order when all -l arguments have been moved to the end of
the command line.
|
|
"pkg_admin audit-history" command to print the full list of
vulnerabilities and use further pkg_admin pmatch logic to mark them as
fixed or still open. For pkg_install versions before 20080415, skip the
vulnerability processing.
Discussed with: dmcmahill
|
|
anyway, simplify logic a bit:
Add Python 2.5 to the default list, but also mark it as incompatible if
wip/python25 is not present. Move the Darwin handling after setting a
default value.
Provide a new variable _PYTHON_VERSIONS_ACCEPTED that is filtered by
PYTHON_VERSIONS_INCOMPATIBLE. This helps to avoid providing broken
dependencies when a version is not supported as PYPKGPREFIX wouldn't be
set in that case.
|
|
|
|
almost two years at some packages (e.g. "openjade") require at least
that version anyway.
|
|
|
|
close PR 38040.
|
|
PLIST_VARS is the list of names corresponding to automatic variables
generated by plist.mk to simplify having conditionally-present entries
in the PLIST. If "var" is listed in PLIST_VARS, then the automatic
variable is named PLIST.var. If PLIST.var is defined, then in the PLIST
generation, the ${PLIST.var} symbol is replaced with the empty string,
or "@comment " otherwise.
|
|
|
|
comes from pkg_install now.
|
|
itself might not.
|
|
|
|
Discussed with jlam.
|
|
|
|
phase pkg_install-depends before bootstrap-depends that just tries to
install a new pkg_install if the current version is too old. Still
keep it as bootstrap dependency for the bulk build code.
For NetBSD, PKG_TOOLS_BIN has to be computed in shell code due to a make
bug.
OK: jlam@
|
|
+ Add a "chroot" option, stolen from pkg_comp(8) that starts a root
shell with a better environment setup.
|
|
|
|
|
|
|
|
|
|
|
|
They are long outdated and not maintained upstream.
Update infrastructure for their removal.
Removal was announced on pkgsrc-users on March 13.
|
|
Both have security problems and are not maintained.
Update infrastructure for their removal.
Removal was announced on pkgsrc-users on March 13.
|
|
problems which manifested in "make update" failing.
|
|
|
|
|
|
bumped in the mean time.
|
|
Remove PostgreSQL 8.0 as choice.
|
|
extract script. This can be used in a more natural way by custom
do-extract targets than EXTRACT_CMD.
|
|
|
|
(Need to consider installing a sane shell as part of bootstrap.)
|
|
happen.
|
|
/bin/sh, the "POSIX.2 compliant" shell, is FUBAR:
$ echo {a,b}
a b
|
|
Instead of just looking at the libraries, we check for the headers as
well, and if multiple implementations exist (usually because of symlinks
to shared libraries), then we order the search as:
tinfo, curses, termcap, termlib, c
|
|
in bsd.buildlink3.mk was broken with pkg_install-20080309 was it
returned a relative path. It would have failed before e.g. with symbolic
links in the path. pkg_info -E is simpler and was added exactly for this
purpose. Fixes PR 38213 and PR 38211.
|
|
|
|
|
|
|
|
BUILD_DEFS_EFFECTS instead of BUILD_DEFS.
|
|
code was moved to the builtin.mk file. The buildlink3.mk file should
contain the bits that always apply to all packages that include it.
The builtin.mk file should include the bits that only apply if
"termcap" is listed in ${BUILDLINK_PACKAGES} (this isn't the case
if we use curses to replace termcap). As such, redistribute the
code as follows:
+ Move the parts that remove -l options for terminal libraries we
don't support, as well as for transforming "-ltermcap" into the
appropriate libraries, from the builtin.mk back into the
buildlink3.mk.
+ Leave the parts the remove -lcurses and -lncurses in the
builtin.mk. We can remove the ${TERMCAP_TYPE} == "curses" check
since that part of the file is protected by CHECK_BUILTIN.termcap,
so it should only be triggered if "termcap" is in BUILDLINK_PACKAGES,
which only happens if ${TERMCAP_TYPE} isn't "curses".
|
|
package does not use either curses or ncurses. We determine this
by inspecting BUILDLINK_PACKAGES and looking for "curses" and
"ncurses".
+ Because the above logic uses BUILDLINK_PACKAGES, the code must be
moved from termcap.buildlink3.mk into termcap.builtin.mk where it
is safe to inspect BUILDLINK_PACKAGES.
|
|
the command line so we don't find any system ncurses library.
XXX This currently causes problems with packages using both termcap
XXX (usually via readline) and curses. This will be fixed in time.
|
|
|
