Not just the spec file, but any other files not in the upstream tarball. E.g. centos specific config files. 1) It works for srpms from all sources. Including those that don't publish a git of their spec files and other meta-data. 2) It yields a very clean boundary between what was 'ours' and what was 'others'. Made the lawyers happy. 3) Before we switched to the 'repo' tools, we had to keep all repos using a common branch name. This created a strong incentive to keep the number of gits to a minimum. On 18-11-01 07:01 PM, Cordoba Malibran, Erich wrote:
Hi all,
As I understand, the meta_patches are patches that are applied to the specfiles for projects where a SRPM is downloaded. This process is something like:
- Unpack srpm - Apply patches to the <project>.spec file. Most of this patches are just modifications to add source code patches. - Create a new srpm with the source, the modified specfile and additional patches that will be applied on build time.
So, having this process, I'm wondering in the need of having the meta_patches instead in just one <project>.spec checked in the repository.
Also, I'm trying to understand the rationale behind these meta_patches.
Thank you in advance.
-Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss