| |
@@ -3110,6 +3110,33 @@
|
| |
in bootstrap still needs an exception from the Packaging Committee
|
| |
as stated in <<General Exception Policy>>.
|
| |
|
| |
+ When importing a bootstrapped package, create a side tag,
|
| |
+ do an initial build in the side tag, change the bootstrap flag,
|
| |
+ then do a new build that can use the initial built package as
|
| |
+ a dependency. A typical session is given below, change package
|
| |
+ name and target names appropriately.
|
| |
+
|
| |
+ [source bash]
|
| |
+ ---
|
| |
+ fedpkg clone my-package
|
| |
+ cd my-package
|
| |
+ fedpkg import my-package-10.0-1.fc43~bootstrap.src.rpm
|
| |
+ git commit -m "Initial import rhbz#233489"
|
| |
+ git push
|
| |
+ fedpkg request-side-tag
|
| |
+ fedpkg build --target=f43-build-side-134096
|
| |
+ koji wait-repo --request f43-build-side-134096
|
| |
+ sed -i "s/%bcond_without bootstrap/%bcond_with bootstrap/" my-package.spec
|
| |
+ git add my-package.spec
|
| |
+ git commit -m "Full package build"
|
| |
+ git push
|
| |
+ fedpkg build --target=f43-build-side-134096
|
| |
+ ---
|
| |
+
|
| |
+ Once done, complete the import through https://bodhi.fedoraproject.org/[bodhi].
|
| |
+ https://hackage.haskell.org/package/fbrnch-1.7#readme[Fbrnch] can help automate
|
| |
+ some of these steps, and is worth using if building many dependent packages.
|
| |
+
|
| |
== System Cryptographic Policies
|
| |
|
| |
Applications which make use the SSL or TLS cryptographic protocols
|
| |
Based on
https://omairmajid.com/posts/2021-04-09-bootstrapping-.net-on-fedora/
and
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BKUPTP6GVZ2CUUJJK22I5ZAW6XGLRYUB/