Splitting out guest scripts into another port called sysutils/xe-guest-utilities. This tracks what NetBSD is doing and at some point in the future we may be able to share a common codebase. Another thing we should consider is renaming sysutils/xen-tools to sysutils/xenstoretools also to mimic what NetBSD is doing since dom0 support is slated for the FreeBSD 10 release. When you have a fully functional dom0 available it makes more sense to have xentools be the tools for the dom0. Here's a list of NetBSD's xen ports to demonstrate what I mean: sysutils/xe-guest-utilities-6.0.2nb3: NetBSD VM tools for Citrix XenServer sysutils/xenkernel20-2.0.7: Xen Kernel sysutils/xenkernel3-3.1.4nb6: Xen3 Kernel sysutils/xenkernel33-3.3.2nb6: Xen 3.3.2 Kernel sysutils/xenkernel41-4.1.3: Xen 4.1.x Kernel sysutils/xenstoretools-4.1.3: Xenstore Tools for Xen 4.1.x sysutils/xentools20-2.0.7nb15: Userland Tools for Xen sysutils/xentools3-3.1.4nb11: Userland Tools for Xen sysutils/xentools3-hvm-3.1.4nb7: Tools for Virtual Machine Extensions support in Xen sysutils/xentools33-3.3.2nb14: Userland Tools for Xen 3.3.x sysutils/xentools41-4.1.3nb2: Userland Tools for Xen 4.1.x Removed file(s): - files/xe-daemon.in - files/xe_wrapper Generated with FreeBSD Port Tools 0.99_6 (mode: change, diff: suffix)
Responsible Changed From-To: freebsd-ports-bugs->swills swills@ wants his PRs (via the GNATS Auto Assign Tool)
State Changed From-To: open->closed Committed. Thanks!