From Developer Community
Overview
The PLDP Build Services are part of the Partner Linux Driver Process and shorten the time between Novell releasing a SUSE Linux Enterprise kernel update and vendors releasing matching drivers.
PLDP Build Service Steps
- The Kernel Module Packaging HOWTO provides detailed step by step instructions.
- Apply for the PLDP Build Service by creating a new bug request. If the request is for an updated version of a previous request you still need to create a new and separate bug request. This can be done at https://bugzilla.novell.com:
- Classification should be "Partner Linux Drivers".
- Product should be “Partner Linux Driver Packages --- Code 9” (for SLES 9, NLD 9 and/or OES 1) or “Partner Linux Driver Packages --- Code 10” (for SLES 10, SLED 10 and/or OES 2).
- Component should be “Kernel Package” (or “Userspace Package” if appropriate).
- Summary should contain the driver vendor name, driver name and driver version (example: "Intel e1000 7.1.9")
- Description should contain the following information using this template (simply cut and paste this into bugzilla and replace data with your info):
Partner Name: (Your company name)
Package Name-Version: (example: intel-e1000-7.1.9)
Target Architectures: (examples: "all" or "i386, x86-64, ia64")
Target Kernel Versions: (examples: "GA", "SP3", or 2.6.5-7.282)
Update Site URL: (optional; note that a Novell update site may only be used for GPL drivers)
Initial Install Format: (optional; examples are DUD or Add-on Product)
- ["Host Site URL" may be a Novell site, a partner site, or blank (if the package will not be distributed via a host site.) Any "Host Site URL" should be agreed upon by Novell and the partner.]
- ["Target Kernel Versions" can be a specific kernel release if required, or simply "GA", or the service pack to target.]
-
- Attachment attach the build.log file from a successful build of the package using the build tool from SUSE's build.rpm. This file can be found at $BUILD_ROOT/.build.log. (usually /var/tmp/build-root/.build.log). This file is necessary to understand that the package did build properly before being submitted to Novell.
- U Taint Flag If requestor desires the module to not reflect a U Taint Flag message when loaded then a L3 support understanding between Novell and requester needs to be confirmed. This can be done in prior communication and/or through the bugzilla entry. By removing the U Taint Flag the module will then report the supported status of external. PLDP L3 support understanding
- Novell Partner Engineering will then evaluate the request and work with you to ensure that the source code is structured correctly to be placed into the partner module area of the SUSE Linux build system.
- Novell Partner Engineering processes requests internally using the following steps:
- Packager is assigned the new bug request.
- Package is built and Signed by assigned packager.
- Package Structure Validated by packager then by the Build Manager.
- Package Delivered by posting on http://forgeftp.novell.com/driver-process/staging/pub/update/ and/or sent directly to the partner for testing and validation.
- Package Validated by partner and notifies Novell if rpm is to be posted on a Novell repository.
- Once the source code has been placed into the build system, the module(s) will be rebuilt with every new kernel release and Novell Partner Engineering will provide the rebuilt module(s) back to you for validation.
