starting order section

This commit is contained in:
YellowJacketLinux 2024-10-19 23:32:19 -07:00
parent 14f973b7fb
commit 4648c20f69

View File

@ -53,3 +53,18 @@ uncompressed duplicates, it does not remove files under RPM management.
The shell script [`remove_duplicates.sh`](remove_duplicates.sh) can be used to The shell script [`remove_duplicates.sh`](remove_duplicates.sh) can be used to
remove the duplicates. Run it once a day or so during the RPM bootstrap process, remove the duplicates. Run it once a day or so during the RPM bootstrap process,
definitely after installing RPM packaged Perl for the first time. definitely after installing RPM packaged Perl for the first time.
Bootstrap Build Order
---------------------
The build order is not *too* important. At the start, the `--nodeps` switch is
often needed because both library and runtime dependencies are in fact present
but not yet under RPM management, so the RPM database does not know about them.
I started with the [`kernel-abi-headers`](SPECS/kernel-abi-headers.spec) package
because it would be easy to restore that `noarch` package if something went
wrong, and I followed that with the [`vim`](SPECS/vim.spec) package because it
tested a binary build and again would be easy to restore the package if
something went wrong.