smd-ros-release/pololu_smc_driver-release — pull request #1 by cottsay (2014-06-30 19:51:52+00:00)
Title: Add RPM generator to action list

This PR adds the RPM generator to the default action list for your package. It means that all future releases will generate an RPM *.spec* file for the package, which can be used to release your package into Fedora.

It is most likely that you will not need to do anything extra to support your package in Fedora. However, there are a few packages that require dependencies that are not available in Fedora. If your package is one of them, please note that here and close the PR, and your package will be excluded from RPM building.

There are other packages that require that certain safeguards and features of RPM generation be disabled. If your package is one of them, you will be notified of the changes that you need to make in order for the changes to happen automatically through bloom upon each package release. Please wait for the initial build of your package for these changes to be noted. These workarounds are typically needed in cases such as:
- packaging binary files that were not built with the rest of the package
- ignoring the supplied compiler flags during compilation
- packaging `.py` files that do not contain valid python code (such as template files). These files are bytecompiled and any syntax errors will fail the build.
- packaging files that are installed outside of `/opt/ros/{distro}` such as udev rules.
- packaging shared object libraries that do not have global execute permissions.

Once you have merged this PR, it is recommended that you perform the initial generation of the RPM *.spec* file yourself so that the workaround repository for your package may be removed. To do that, please run the following commands on your package:
```
git-bloom-generate -y rosrpm --prefix release/hydro hydro -i ???
```
```
git-bloom-generate -y rosrpm --prefix release/indigo indigo -i ???
```
where ??? is the current release number used on your package. It is very important that you have the newest version of `bloom` when doing so!

This initial generation will not affect the Ubuntu package at all. If you choose not to perform it now, the workaround repository will continue to enable Fedora support of your package until the next time you release the package.

For more information on RPM generation, see the tracking issue at (INSERT TRACKING ISSUE LINK HERE).

Thanks,

--scott