Remember, there's a 'base' base domain shared between build trees, and 'local' domains dedicated to a build tree. If KVM_PREFIXES is used, multiple local domains are possible.
The following changes are in place: - the base domain (swanfedorabase, swanfedora22base, swanfedora26base) is only required when first creating the local domains i.e., once the local domain suite is created, 'base' can safely be deleted using 'make kvm-uninstall-base-domain' if ever it doesn't exist and is needed, it will be created again - make kvm-upgrade aka make kvm-upgrade-local-domains this is now the 'official' way to upgrade an existing suite of local domains. It deals with details like rebuilding the test domains. It doesn't touch or require the 'base' domain (if you really really want to upgrade the base domain use 'kvm-upgrade-base-domain') - make kvm-install-hive (experimental) this first installs libreswan onto a dedicated local build domain, and then clones the build domain creating the relevant test domains with libreswan pre-installed if you have lots of test domains this is likely faster; this might become the default Once the above has settled, I'm also looking at: - change the default 'base' domain to 'swanfedora22base' (currently it is swanfedorabase) the next time a local domain suite is created this would be created two; but not before this sets us up for the switch to fedora26 which will get the name swanfedora26base - add/use a dedicated 'build' domain for building currently builds are performed using 'east' (the choice was arbitrary); and 'east' doesn't have internet connectivity; in contrast 'build' does so it can do stuff like download huge test vector files the hive builds already use this Andrew
_______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
