🏠 Go home.

Fedora Packaging via Vagrant

Published on

So, neat, I'm doing Fedora stuff again. I'm about at the point where I want to reinstall my laptop, however, with an up-to-date copy of my Ansible laptop provisioning scripts; I don't have to maintain two machines now with it, so I can clean some stuff up, which is awesome. To make things easier on myself both now and in the future, I decided to leverage this neat little VM building tool called Vagrant to build my Fedora dev environment.

It's incredibly simple, but lets me create and throw away Fedora development environments every time I want to do a package build; previously I'd have to rely on things like rpmdev-rmdevelrpms, which would inevitably try to remove something like VirualBox because of its dependencies on kernel-headers. With this I just need Ansible, Vagrant and VirtualBox on a given host, and can instantiate a Fedora development environment in like 3 minutes. Pretty great stuff, imo.

The even niftier thing is that, given a Fedora 20 Vagrant Box which could instantiate EC2 instances, I could spin up nice beefy boxen just to do builds whenever I wanted it. My own private Build Servers, but womp womp.

I could have spent the six or seven hours it would have taken to get a local Mock installation running, but I don't really … want to do that. I'd rather spend those six or seven hours being absolutely terrible at integrating patches that people give me to fix my packages' bugs… woops.

Respond to this note:

Ryan Rix is a privacy rights advocate and net-art wannabe. Reach them on the Fediverse as @rrix@cybre.space, twitter as @rrrrrrrix, via email to ryan@whatthefuck.computer or on Facebook or on Matrix as @rrix:whatthefuck.computer.