From now on, building ports requires X11BASE.
* lots of ports missed this variable (porters always have X11 installed)
jasper made a first pass on fixing these, but no doubt it will drift
away soon
* users should use packages
* people building ports should know what they are doing and having
X11BASE as a requirement is perfectly reasonnable
* we are merging config.x11.site into config.site because of a stupid
autofoo bug ; currently when USE_X11 is set, some ports may loose the
ability to even load config.site
tested on a bulk by landry@
ok robert@ jasper@ landry@ sthen@ naddy@ "I won't cry if it dies" espie@
in the distfiles. defaults to installing files from examples/. but
that can be set via MODCPAN_EXAPLES_DIST. please see port-modules(5) for
more information.
feedback and ok espie@
by default for ports that set USE_LIBTOOL=Yes. Faster, better,
stronger, and cuts bulk builds time by ~15% in my tests on amd64.
Volunteers welcomed to fix the few USE_LIBTOOL=gnu users in the tree.
Report any oddities to ports@...
'Go ahead' espie@ 'Please proceed' steven@
ok ajacoutot@ jasper@ phessler@ sthen@
helps getting past shell quoting errors, so that the infrastructure
will report actual trouble (is also simpler than :S/<...>/ for pkgspecs).
REQUIRES CURRENT MAKE TO WORK!!!
PACKAGE_COOKIE, so that print-plist-contents keeps working.
Only the packaging part (e.g., PACKAGE_COOKIES) should be affected.
Alter PKGNAMES while we're there, as it's only used for debugging, and
it's better that way.
(fixes pkgmklocatedb)
More precisely:
- for "older" libspec in LIB_DEPENDS, only compare them against
the libs from the LIB_DEPENDS.
- check LIB_DEPENDS against all libspecs for the package (both from WANTLIB
and LIB_DEPENDS) to turn them into LIB_DEPENDS.
- create a full list of installed libs and of 'inter-package' libraries to
solve all WANTLIB in one go.
This is actually faster than the old code, but a bit more complicated.
In particular, create a tmp package until we're certain it is okay
(thanks to register-plist). -> remove race condition in dpb3, which
assumes a package existing is enough for it to proceed.