Open Ethernet Networking (OpEN) API Guide and Reference Manual  3.6.0.3
Adding new RPMs

Broadcom uses CentOS 6.2 source code RPMs as the basis for its binary RPM packages. If additional RPMs are to be added, then it is recommended that CentOS 6.2 source packages be used as the basis as this will avoid any complications with dependencies on existing packages. The CentOS 6.2 source repository can be accessed at http://vault.centos.org/6.2/os/Source/SPackages/.

The steps below highlight how to add an RPM to the build process. These steps assume that the RPM is named <package>.rpm.

Updating New RPMs for Broadcom Linux Compilation

The tasks involved in updating a new RPM for compilation for Broadcom Linux can vary widely depending on the techniques used in the <package>.spec file to create the RPM. Typical changes are listed below. Note that in some cases a patch file must be created to patch the CentOS supplied source code. See further information on the patching procedure see the section on Creating Patch Files.

If you compare the spec files for packages supplied by Broadcom to those available in the CentOS vault then you will see the types of changes that are described above.

Creating RPM Patch Files

If you need to change a source code file from a package then you should do so using a patch. For example, suppose you want to make some modifications to file.c which is in the mydir directory of the mynewpackage-1.2 package:

Note that you can build up changes to multiple files in the single mynewpackage-cross.patch file by concatenating new diff output to the end of the file.

If you make a mistake and need to make subsequent changes then be careful that the files in BUILD are those with as many patches applied as possible. In some cases in order to get a clean file.c to compare against you have to comment out the "%patchNN" line and start the build again.