vmware image is too small to do any work, expand to 2GB

[scottmc]

Trying to do any work in a 700mb haiku VM is painful. Sure we can boot it and then install to the empty 2GB image, but why should we have to jump through extra hoops to be able to get any work done? Let's get this done before the next release.

[scottmc]

something like this, but also including releases.

diff --git a/build/jam/ReleaseBuildProfiles b/build/jam/ReleaseBuildProfiles
index 0fc925f..678900c 100644
--- a/build/jam/ReleaseBuildProfiles
+++ b/build/jam/ReleaseBuildProfiles
@@ -41,7 +41,11 @@ switch $(HAIKU_BUILD_PROFILE) {
                AddGroupToHaikuImage party : 101 : user sshd ;
                HAIKU_STRIP_DEBUG_FROM_OPTIONAL_PACKAGES = 1 ;
                HAIKU_IMAGE_HOST_NAME = shredder ;
-               HAIKU_IMAGE_SIZE = 600 ;
+
+               switch $(HAIKU_BUILD_PROFILE) {
+                       case "nightly-vmware" : HAIKU_IMAGE_SIZE = 2000 ;
+                       case "*" : HAIKU_IMAGE_SIZE = 600 ;
+               }

                AddOptionalHaikuImagePackages Pe Nano Vision P7zip XZ-Utils ;
                AddOptionalHaikuImagePackages Development Git OpenSSH OpenSSL ;

[bonefish]

If we supported VMware images that resize automatically that wouldn't be a big deal, but since we don't the image would take a lot more space. Besides, I don't see why you don't just use a second disk image to contain all your work. That's a good approach anyway, since it allows you to just update to a newer Haiku without losing your work by just replacing the system image. That's how I do it even with real partitions.

If you build your own image, you can just override the image size in you UserBuildConfig.

[scottmc]

This is no longer an issue, as users can create a vm from the anyboot images.