Time has passed, and what was new is now crufty. Update descriptions,
and remove pointers to bulk builds that are no longer. Add a brief
explanation of SDK versions and a pointer to the code that
queries/sets them.
libarchive 3.3.3:
Avoid super-linear slowdown on malformed mtree files
Many fixes for building with Visual Studio
NO_OVERWRITE doesn't change existing directory attributes
New support for Zstandard read and write filters
Running bootstrap with short options (like -q for --quiet) is not
implemented. Therefore, instead of silently ignoring such options, fail
with an appropriate error message.
If not, set _OPSYS_SUPPORTS_SSP=no during bootstrap and in mk.conf.
Do SSP detection on "SunOS", and let mk/platform/SunOS.mk's default
"yes" be overridden in mk.conf.
No change to generated mk.conf on NetBSD 8 or CentOS 6. Fixes bootstrap
on Tribblix.
* Put indentation right to follow the existing style
* Correct wrong justification for need of pax on Arch: pax (and not PaX) is
only provided throw https://aur.archlinux.org/packages/pax/ and get low
support (currently broken)
This avoids errors when running from a read-only pkgsrc checkout as the
resulting packages cannot be written to the default PACKAGES directory. The
binary packages aren't useful anyway, as they are often built with reduced
configuration options due to the limited bootstrap environment.
Fixes issue reported by Julien Savard and others.
This is based on the decision The NetBSD Foundation made in 2008 to
do so, which was already applied to src.
This change has been applied to code which is likely not in other
repositories.
ok board@, reviewed by riastradh@
Both sed and awk in the Chrome OS base are permanently put into sandbox
mode, which makes them unsuitable for pkgsrc use. We were already building
nbawk; also add nbsed.
Since Chrome 64, /usr/bin/awk has been a version of mawk that is permanently
in restricted mode. Notably, this means it cannot run pipes, which pkgsrc
requires. Use nawk.
When bootstrap is run with --cwrappers=no (or yes, for that matter),
the value is written into mk.conf at the end of the bootstrap but not
used _during_ the bootstrap itself. Thus, when bootstrapping on Linux
with no builtin diffutils, cwrappers ends up indirectly depending on
itself, and there is no way around that. This commit fixes this.
Eric Brown: PR pkg/52567: Readme.MacOSX is out of date
Additional changes by me: don't mention that the file isn't README.OSX
due to OS X being a different name, because the new name macOS makes
the filename less confusing.
Since cwrappers was enabled by default on some platforms, it became
effectively impossible to bootstrap without cwrappers there.
With this change "--cwrappers" needs to be set to "auto", "yes" or "no"
explicitly when used.
No functional change intended without specifying "--cwrappers" (or with
"auto").
Submitted on tech-pkg@ with no objection.
release, state that instructions only apply to legacy release.
- State that only the compler in base is currently support.
- Update the list of tested releases.
indirectly via it being pulled in using USE_CWRAPPERS=auto, we need to
ensure that it is not built with -DPKG_PRESERVE as otherwise it interacts
badly with pbulk's pkg_delete test.
Substantially revise the ABI 32/64 discussion, separating the
close-in-time changes about the default ABI vs how it is encoded.
Thanks to jperkin for off-list clarifications.
