1
edit
Changes
no edit summary
ExclusiveArch: x86_64 aarch64
</source>
* When commenting out a existing line of code, add one more '''<tt>%''' </tt> before any rpm macro otherwise rpmbuild will treat it as a error/warning. For instance:
<source lang=bash>
# Before commenting out
</source>
* Add '''<tt>.leap''' </tt> after the release version, add '''<tt>.leap.1'''</tt>, '''<tt>.leap.2''' </tt> ... and so on for further modifications
* Make sure to specify all the changes under the <tt>%changelog</tt> section:
=== Rebranding ===
The packages that contain the word ''extension <tt>.centos'' </tt> in their release version are branded packages. In order to properly rebranding re-branding those packages for LEAP, here is the checklist:* Replace the word ''"CentOS'' " or ''"CentOS Linux'' " with ''"LEAP'' " in spec package descriptions and patches (make sure they are branding-related)
* Replace CentOS branding patches with LEAP branding patches
** If certain patch file contains author name, regenerate the patch with your own name instead of modifying the patch directly
* Remove CentOS/RHEL certificate files and binaries
==== Particular branded packages cases ====
; libreport / abrt
: Libreport and abrt are the library and application for automatic bug detection and reporting to RHEL bug tracker servers. Since CentOS added several significant patches to both packages for supporting their own bug tracker, removing those patches can be very complicated process. The best way to solve this problem is retrieving the original RHEL versions from http://git.centos.org, add our own de-branding patches, and bump the version-release number + ''.leap'' to match the requirements of dependency.
* xorg-x11-drv-dummy and xorg-x11-drv-fbdev
= Fixing dependencies =
After all of the packages have been done, it's time to fix minor broken dependencies. <tt>repoclosure</tt> and <tt>leap-closure-report.sh</tt> (by '''Chris Markieta''') are the tools to check dependency stats of a repository. You should always check the build-tag repository instead of dest-tag because build-tag usually inherits all the existing packages.
When a package requires a missing shared library file like <tt>xxxxx-3.so</tt>, the package usually only need to be rebuilt again in order to pick up the latest .so file from the latest version of required library.
= Package signing =
= Synchronizing Repositories =
= Release =
More coming ...
