On my dev server I am running Percona (5.5.27), and have just spun up another server to act as a staging area for public access to a new project. I am trying to control package versions by using yum plugin 'versioncontrol', but for some packages this approach doesn't seem to be working and I think the reason is; the upstream source for the specified version is no longer available (current version is 5.5.32). For packages like httpd this really isn't an issue and versionlock works fine, as the CentOS upstream doesn't update too often and the version I installed on the dev server (over a year ago) is still available.
But what do I do to ensure the same Percona version (5.5.27) is available to all my existing and future servers? Do I build an rpm, or is there another approach?
If I am to create an RPM, is it possible to do it for a specific package, or series of packages? Can I create an rpm with the following packages, resulting in a single rpm?
Percona-Server-client-55-5.5.27 Percona-Server-devel-55-5.5.27 Percona-Server-server-55-5.5.27 Percona-Server-shared-55-5.5.27 Percona-Server-shared-compat-5.5.27
A lot of questions, but as a lesser skilled sys admin I have put off building rpms for as long as I could.