ReleaseEngineering/ToolsPackaging
Contents
Tools Packaging
This section of the Wiki describes how Mozilla's Release Engineering team aims to package it's tools. There are currently mostly ad-hoc tools for packaging the tools we build with, but there is an effort to make these packages generic and redistributable.
This page and those located under it describe packaging done using newer tools that aren't ad-hoc.
Fedora, CentOS and Rhel
There are two repositories that the spec files we deploy are stored in:
The first repository contains ad-hoc packaging specfiles and the second contains specfiles that are more generic and have tooling in place to make building the packages a lot easier.
The general rule of thumb is that if you are working on Mozilla infrastructure using PuppetAgain, you should be using the 'releng-rpms' repository.
There are a few common things that you are probably interested in doing if you are reading this page
- Guidelines for packaging -- please read this
- Building or Updating an RPM -- creating a new package or updating an existing one?
- Generating or deploying to a Yum Repository -- deploying a new rpm to our mirrors
Contributions
You want to help? Awesome! If you have patches that you'd like us to merge, please make sure that you:
- follow the guidelines for packaging
- have a patch that contains your spec, your lookaside file and any small files to be checked in
- links to any tarballs that you've downloaded from upstream sites
- directions for recreating self-created tarballs from code repositories
When you've done that please submit a github pull request. If you don't have a github account, please file a bug using this template
Useful Documentation
Mac OS X
No work done here at this point
Windows
No work done here at this point