This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
pciquirk.py: fix uninitialized variable when there's no PERMISSIVE_CONFIG_FILE
add a note about exported PCI devices in netbsd1 example file
Python hacking by Pierre-Emmanuel Le Roux at LIP6 (thanks !)
PKGREVISION++
- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
for the first time. This cause a race between xenconsole and xenconsoled,
where the later start writing to the master pty before the former has
switched it back to raw, causing some lines to be echoed back to the
domU.
Fix this by keeping the slave open in xenconsoled, so that when xenconsole
opens it attributes are not reset. Hint provided by fvdl@, thanks !
Because of this we no longer need to set the slave to raw in xenconsole,
so shorten patch-cc.
Bump PKGREVISION.
from files/ (which have the old IOCTL_PRIVCMD_HYPERCALL to be compatible
with NetBSD 4.0).
Properly handle the new IOCTL_PRIVCMD_HYPERCALL ioctl if present.
Package changes:
point HOMEPAGE to http://xen.org/
looks like the Xen peoples won't put a tarball on their http server
for this; I built one from their repository and put it in
${MASTER_SITE_LOCAL}
Summary of changes since 3.1.0:
some of our patches have been integrated upstream, thanks to Christoph Egger
various performances improvements and bug fixes, including some security
fixes, and one bug that would lead to floating point register
leak/corruption from HVM to PV guests on Intel VMX CPUs.
in version numbers, and upgrade to 3.1.0.
Changes since 3.0.4:
* XenAPI 1.0 support
o XML configuration files for virtual machines;
o VM life-cycle management operations; and
o Secure on- or off-box XML-RPC with bindings for many languages
* Basic save/restore/migrate support for HVM (e.g. Windows) VMs;
* Dynamic memory control for HVM guests;
* 32-on-64 PV guest support (run PAE PV VMs on a 64-bit Xen!); and
* Blktap copy-on-write disk support.
It also fixes some HVM bugs.
