generic/ vs roboxes/ namespace?

[mcandre]

Which namespace should users prefer when referencing these boxes from Vagrant Cloud, the "generic" or "roboxes" namespace? Will one become deprecated in favor of the other over time?

[ladar]

The boxes are identical. The descriptions are slightly different to facilitate search variations.

I've been publishing the generic boxes for 2+ years, and that is what I tend to check/use. I only added the 'roboxes' name ~6 months ago, when I finally settled upon a project name.

I expect to upload all of my generic base images to both orgs indefinitely.

If you're looking to pick one, the generic boxes are more popular (because they've been around longer), and thus I'm more likely to hear about an image/problem with one of those (like a corrupted upload) than the less popular roboxes.

[mcandre]

One more thing to clarify: Are the boxes bitwise identical between the generic and roboxes namespaces? Or are the contents potentially a little different, using different build artifacts?

I ask because troubleshooting any problems with these guests could get more confusing when the images are not identical.

[ladar]

They used to be built seperately, but that was very inefficient. So as of late, I've been merging box configurations, and simply exporting the boxes using the alternate names. In other words, the roboxes are exported from the generic virtual machine images. As such the virtual disks should be identical, but the export process may rename files, etc, inside the box file. Not 100% sure.