[Rpm-maint] [rpm-software-management/rpm] Merge buildprocess.md contents into rpmbuild man pages (PR #4047)

[Michal Domonkos]

@dmnks commented on this pull request.



> +	. Export build environment to *%builddir*/_rpmbuild.env_ file
+. Build sources and populate *%buildroot*
+	. Unpack sources and apply any patches (*p*, *%prep*)
+	. Generate dynamic build dependencies (*d*, *%generate_buildrequires*)
+	. Check dynamic build dependencies
+	. Configure sources (*f*, *%conf*)
+	. Compile sources (*c*, *%build*)
+	. Install binaries into *%buildroot* (*i*, *%install*)
+	. Read dynamic spec parts
+	. Execute tests (*k*, *%check*)
+. Process files to be packaged
+	. Collect source files
+	. Collect binary files in *%buildroot* based on *%files*
+		. Add regular entries
+		. Add documentation entries (*%doc*)
+		. Add license entries (*%license*)

They're listed separately so that the corresponding spec sections can be shown in parentheses for each. That's one of the purposes of this build process breakdown, to let the user make sense out of the rpmbuild output, and these are (internal) scriptlets that get executed and logged in the output separately.

We could still merge them and put both spec sections into parentheses, but that would (kinda) defeat the "format" established in the introduction text where stage identifier is followed by a spec section :smile: So dunno.

As for the entities, they don't seem that much different from regular files, what happens internally is basically this:

1. `addPackageFileList()` for normal (non-special) entries in `%files`
2. `processSpecialDir()` for special `%doc` entries in `%files`
3. `processSpecialDir()` for special `%license` entries in `%files`

These two scripts do indeed *copy* files to buildroot first, but then they also *add* them to the internal file list structure via `processBinaryFile()`, much like the "normal" files.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4047#discussion_r2550337526
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/4047/review/3493537488 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20251121/436a8b79/attachment-0001.htm>