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

[Michal Domonkos]

@dmnks commented on this pull request.



> +	. 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*)
+	. Perform file classification
+	. Generate runtime dependencies using *rpm-dependency-generators*(7)
+	. Check packaged files against *%buildroot* (*l*)
+. Create packages
+	. Write binary packages to disk (*b*)
+	. Write source packages to disk (*s*)
+. Clean up
+	. Perform explicit clean up - OBSOLETE (*%clean*)
+	. Perform implicit clean up (*rmbuild*)

> Explicitly stating most of these are optional and depend on the spec (before the list) would go a long way. Right now, the "if either is given" sets the stage that exceptions like that will be noted, and then when there aren't any, it looks like all the following steps are mandatory.
> 
> The main cases are of course the build scriptlets that a spec might or might not have, and then the file processing section which can get skipped because not all packages contain files.

Yep, good points!

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

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