turns the diagnostic messages like
WANTLIB += foo bar
to
WANTLIB-subp += foo bar
when checking the libraries in a subpackage.
OK and lots of help and improvements from espie@
build, use a new DPB_PROPERTIES "later" that informs the Grabber to build
it during a second stage (with the exact same rules as before).
And thus, reconnect quirks into the "normal" build.
Main difference: other databases like sqlports or pkglocatedb will index
quirks again
during the current run, we rm any quirks packages that could be left over
from a previous build first.
This ensures quirks gets rebuilt if some packages did change, so that
the updateinfo cache is as fresh as possible.
by aja@ and landry@
My error was that I did think I needed a placeholder in the new list to
tack new stuff to, whereas I actually need the placeholder in the old list,
so that it gets copied along with the stuff that's attached to it...
* Complain where $OpenBSD$ was previously mandatory.
* Still complain where it continues to be forbidden.
* Also check the content of the "files" directory.
ok sthen@
(misses the fragment dispatch)
generalize "tweak_other_paths" to run *after* the normal recognition, since
ocaml paths are linked in more generic ways that just "parent directory for
fonts", so they don't necessarily occur in the right order, and we shouldn't
care.
better to install all sets by default, even though this makes the chroot
more costly (slightly).
So hard-code them for now, grabbing them off SHA256 is on the TODO list
- Add a version argument (second) to modgo-gen-modules-helper.
- Change modgo-gen-modules target to fetch module info for the
current MODGO_VERSION of a port. Setting MODGO_VERSION=latest
will fetch the latest version the Go ecosystem knows about.
Similarly, if MODGO_VERSION is empty, fetch the latest
verstion Go knows about.
While here:
- Add '-trimpath' to MODGO_FLAGS.
OK danj@
These were previously used to automatically add tags to PLIST for
Haskell library ports. Since library ports no longer exist, such
tagging only ever triggers for ghc package where it is now harmful.
ok kili
human-readable way, and compare them, so that people can figure out if
the version parsing did cope with whatever scheme upstream came with.
should alleviate the need for EPOCH in many cases
