[Rpm-maint] [rpm-software-management/rpm] RFE: Automatic (sub)package generators (#329)

[Ikey Doherty]

In ypkg we have a _priority based_ pattern system, which will also happily accept absolute paths.
Internally we define subpackages by way of distribution policy, which as well as automating much of the packaging process, ensures distribution policy is respect for file and subpackage placement.

We place dbginfo packages at a significantly higher priority than stock built-in patterns, and the `package.yml` priority is considered the ultimate priority, enabling the package maintainer to override default considerations (i.e. soname patterns where the upstream has abused .so versioning)

Internally this is handled through a `PackageGenerator` concept and is initially modeled around the Clear Linux autospec project, and in combination with our dependency system ensures subpackages have natural relationships between one-another and the parent package.

At this point you're already operating on the notion of generators - with either patterns or cheap absolute paths. This allows a global file table which ensures that files do not conflict **within** a package set, something seen quite commonly with `.src.rpm` inter-file-conflicts. A paths position is mutually exclusive within the set. At this point it becomes trivial to extend these generators with support for selinux policies, or indeed, simple `.in` substitution (patterns could conceivably be extended to support `%libdir%` style macros and expanded at runtime.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/329#issuecomment-333832971
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20171003/a29a966f/attachment.html>