lavabit / robox

The tools needed to robotically create/configure/provision a large number of operating systems, for a variety of hypervisors, using packer.
620 stars 139 forks source link

POLL: Alter dragonflybsd, hardenedbsd, netbsd, openbsd repo names. #223

Closed ladar closed 2 years ago

ladar commented 2 years ago

I'm asking the community for their opinion on a proposed change boxes named in the title. The proposed change would involve using the same strategy we already use for gentoo and arch, and applying it to the dragonflybsd, hardenedbsd, netbsd, openbsd boxes. In laymen terms this would mean that instead of having multiple repos for each distro, with the each repo tied to a specific release, we'd switch to only maintaining a single repo for those boxes that tracks the current release.

On the upside, this would mean fewer boxes would need to be created, which would give us room to keep expand in other areas. The downside would be that the generic/roboxes repos for dragonflybsd5, dragonflybsd6, hardenedbsd11, hardenedbsd12, hardenedbsd13 netbsd8, netbsd9, openbsd6, openbsd7 would no longer be updated, and eventually disappear. This would break existing configs, although the change would likely only involve updating the config to point at the new generic/roboxes repos called dragonflybsd, hardenedbsd, netbsd, and openbsd.

I'd like to solicit feedback from the community before making a decision, which will likely come sometime in the first part of next year. If you would like us to make this change, just mark this post with a thumbs up. You only need to leave a comment if you have a strong argument that hasn't already been expressed. If you DO NOT like this idea, and want us to continue with the current strategy, then please leave a comment explaining why (or, if someone has already made the same argument, simply reference the existing reply).