If you're read our http://brlcad.org/wiki/Deuces page, then you're probably familiar with our virtual disk image that helps users get started:
- https://sourceforge.net/projects/brlcad/files/BRL-CAD%20for%20Virtual%20Machines/
This task involves updating that disk image so that it contains an up-to-date version of BRL-CAD. Update the provided README-VM.txt file so that it's even more simple and easy to use the image. Remove references to the Google Summer of Code (it's really for anyone). Remove any unnecessary information. Most importantly, update the sources to and install of BRL-CAD contained within the disk image. To do that, you need to be familiar with Subversion. Make sure it compiles and installs cleanly (run make clean like our configuration notes describe).
Pay close attention to everything that you do within the VM as that will be contained within the disk image. Keep a log of EVERYTHING you do to the image and the documentation and submit that text file here (along with an external link to your updated image, it's too big to upload to the GCI melange website).
You can submit the updated image to our patches tracker on Sourceforge.
You need to be meticulous to complete this task successfully. If you're not a stickler that can pay attention to details, do not try to take this task on.
| File name/URL | File size | Date submitted | |
|---|---|---|---|
| vm_update.zip | 145.5 KB | December 27 2012 14:09 UTC |
I would like to work on this task.
This task has been assigned to Cezar. You have 72 hours to complete this task, good luck!
The work on this task is ready to be reviewed.
Since the VM is a large file, I didn't upload it anywhere yet. The zip file contains the updated readme (README.txt), as well as the changes I made inside the VM (STEPS.txt). If they look good, I will post a link to the actual VM.
Cezar, that looks really good. The dev-7.22.1 is correct, not .0 since that would be for a rel- version. The bullet failure is interesting (worthy of task?). As for the README and brlcad-build, I believe that was cleaned out due to the VM size getting a little out of hand. What are you up to and how does that compare with what's up on sourceforge now?
It would be nice if the README instructions could be condensed a lot more. That's too much to read and there's some technically unnecessary/distracting information (e.g., aliases).
Congratulations, this task has been completed successfully.
Yes, I think the Bullet failure could be fixed as a task. My ova is 3.37 GB, twice the size of the original. Imported, it's almost 10 GB. Pretty large. I'll try condensing the README even more.
Where's the extra size coming from? Did the original not have BRL-CAD pre-installed?
I forgot to remove the previous installation, but even now, the VM is 9.55 in size and the *.ova is the same. Could all the updates amount to so much space?
Unlikely that space is related to updates. You should figure out where all the space is going. What are your top-100 directories, for example. How do those compare with the old and new?
Something like: find / -type directory -exec du -ks {} \;
will probably take a long time, but should give you comparable output. Variations should run a heck of a lot faster.
Apparently, it's because I kept the brlcad-build directory. Should I remove the contents?
Could it be because of the docs? With the conversion to DocBook, it now generates quite a lot of PDFs.
I got the Readme down to 288 words, is this enough?
The docs may add some, but I'd be very surprised if it was anywhere near 6.5GB... :)
The build directory should have cmake already run, perhaps even make, but then followed by make clean so there are no object build files left. How big is it then?
Hard to say if 255 words is enough without reading it, but that definitely "sounds good" on the surface. I'll get in touch with you later via IRC to look it over (or have you update the docs and files on sourceforge and our site as a task).
The sizes I posted were those of the .ova and .vmdk files. Running 'sudo du -hsx / | sort -n -r | head -n 10` inside the updated VM outputs `5.0G /`, which seems fine.
I ran "sudo du -hs /" on both the original and the updated VMs and I get 4.3 and 5.0 GB. 700 MB seems fine, but I don't know why the .vmdk and .ova are double in size.
My guess is that they're expandable disk images. So while they're both about the same size internally when loaded into the VM, the other was filled considerably more at one point so the disk was expanded to hold more. There should be a way to compress the file back down, something like http://www.ehow.com/how_7397891_compress-vmware-instance-file.html