Skip to content

lru-packages/lru-buildbox-centos7

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

19 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Building custom RPM packages

The repositories that are part of this GitHub organization all have the following pre-requisites.

Prerequisites

Install these on your local computer.

Updating your Vagrant Plug-Ins

This is simply a good thing to do from time to time.

vagrant plugin update

Bring-up the VM

  1. Launch the Vagrant environment. This virtual machine is custom-designed for building CentOS 7 RPM packages, and is configured appropriately.

    vagrant up
  2. Once it's running, log into the Vagrant environment.

    vagrant ssh

Setting-Up Tooling

This VM assumes that you're hosting your package repo in Amazon S3. If not, feel free to install your preferred set of tools and configurations.

While the Unified AWS Command-Line Tools are pre-installed, they are not pre-configured. Please follow the Getting Started Guide for configuring your tools.

Building New Packages

If you want, for example, to build a new git package:

  1. Switch to root.
  2. In /vagrant, run ./pull.sh.
  3. Clone the lru-packages/package-git.
  4. Follow the build instructions in the README file (usually just make). This will copy the resulting RPMs to /vagrant/repo.
  5. Go into the /vagrant/repo directory and make sure the RPMs end up in either el7/x86_64/ or nodist/x86_64/.
  6. In /vagrant, run ./createrepo.sh.
  7. In /vagrant, run ./push.sh.

Syncing

There are a couple of scripts included which facilitate syncing new packages between S3 and your VM. See pull.sh and push.sh for more information.

Contributing

Here's the process for contributing:

  1. Fork LRU BuildBox to your GitHub account.
  2. Clone your GitHub copy of the repository into your local workspace.
  3. Write code, fix bugs, and add tests with 100% code coverage.
  4. Commit your changes to your local workspace and push them up to your GitHub copy.
  5. You submit a GitHub pull request with a description of what the change is.
  6. The contribution is reviewed. Maybe there will be some banter back-and-forth in the comments.
  7. If all goes well, your pull request will be accepted and your changes are merged in.

Authors, Copyright & Licensing

See also the list of contributors who participated in this project.

Releases

No releases published

Packages

No packages published

Languages