mkae commands consistent
All checks were successful
mkdocs build / build (push) Successful in 29s

This commit is contained in:
Louis Abel 2024-05-21 13:12:42 -07:00
parent 0d97374b1c
commit ff34d5ee9b
Signed by: label
GPG Key ID: 2A6975660E424560
3 changed files with 11 additions and 11 deletions

View File

@ -89,13 +89,13 @@ Note that for each of these commands, it is fully expected you are running
``` ```
# Syncs all repositoryes for the "9" release # Syncs all repositoryes for the "9" release
% poetry run sync_from_peridot --release 9 --clean-old-packages % poetry run sync-from-peridot --release 9 --clean-old-packages
# Syncs only the BaseOS repository without syncing sources # Syncs only the BaseOS repository without syncing sources
% poetry run sync_from_peridot --release 9 --clean-old-packages --repo BaseOS --ignore-source % poetry run sync-from-peridot --release 9 --clean-old-packages --repo BaseOS --ignore-source
# Syncs only AppStream for ppc64le # Syncs only AppStream for ppc64le
% poetry run sync_from_peridot --release 9 --clean-old-packages --repo AppStream --arch ppc64le % poetry run sync-from-peridot --release 9 --clean-old-packages --repo AppStream --arch ppc64le
``` ```
{% include "resources_bottom.md" %} {% include "resources_bottom.md" %}

View File

@ -41,12 +41,12 @@ Each repository or set of repositories are controlled by various comps and pungi
First, the toolkit must be cloned. In the `iso/empanadas` directory, run `poetry install`. You'll then have access to the various commands needed: First, the toolkit must be cloned. In the `iso/empanadas` directory, run `poetry install`. You'll then have access to the various commands needed:
* `sync_from_peridot` * `sync-from-peridot`
* `build-iso` * `build-iso`
* `build-iso-extra` * `build-iso-extra`
* `pull-unpack-tree` * `pull-unpack-tree`
* `pull-cloud-image` * `pull-cloud-image`
* `finalize_compose` * `finalize-compose`
#### Full Compose #### Full Compose
@ -54,7 +54,7 @@ To perform a full compose, this order is expected (replacing X with major versio
``` ```
# This creates a brand new directory under /mnt/compose/X and symlinks it to latest-Rocky-X # This creates a brand new directory under /mnt/compose/X and symlinks it to latest-Rocky-X
poertry run sync_from_peridot --release X --hashed --repoclosure --full-run poertry run sync-from-peridot --release X --hashed --repoclosure --full-run
# On each architecture, this must be ran to generate the lorax images # On each architecture, this must be ran to generate the lorax images
# !! Use --rc if the image is a release candidate or a beta image # !! Use --rc if the image is a release candidate or a beta image
@ -76,7 +76,7 @@ poetry run pull-cloud-image --release X
# This ensures everything is closed out for a release. This copies iso's, images, # This ensures everything is closed out for a release. This copies iso's, images,
# generates metadata, and the like. # generates metadata, and the like.
# !! DO NOT RUN DURING INCREMENTAL UPDATES !! # !! DO NOT RUN DURING INCREMENTAL UPDATES !!
poetry run finalize_compose --release X poetry run finalize-compose --release X
``` ```
#### Incremental Compose #### Incremental Compose
@ -86,7 +86,7 @@ It is possible to simply compose singular repos if you know which ones you want
``` ```
# Set your repos as desired. --arch is also acceptable. # Set your repos as desired. --arch is also acceptable.
# --ignore-debug and --ignore-source are also acceptable options. # --ignore-debug and --ignore-source are also acceptable options.
poetry run sync_from_peridot --release X --hashed --clean-old-packages --repo X,Y,Z poetry run sync-from-peridot --release X --hashed --clean-old-packages --repo X,Y,Z
``` ```
## Syncing Composes ## Syncing Composes

View File

@ -31,16 +31,16 @@ Each repository or set of repositories are controlled by various comps and pungi
First, the toolkit must be cloned. In the `iso/empanadas` directory, run `poetry install`. You'll then have access to the various commands needed: First, the toolkit must be cloned. In the `iso/empanadas` directory, run `poetry install`. You'll then have access to the various commands needed:
* `sync_sig` * `sync-sig`
To perform a compose of a SIG, it must be defined in the configuration. As an example, here is composing the `core` sig. To perform a compose of a SIG, it must be defined in the configuration. As an example, here is composing the `core` sig.
``` ```
# This creates a brand new directory under /mnt/compose/X and symlinks it to latest-SIG-Y-X # This creates a brand new directory under /mnt/compose/X and symlinks it to latest-SIG-Y-X
~/.local/bin/poetry run sync_sig --release 9 --sig core --hashed --clean-old-packages --full-run ~/.local/bin/poetry run sync-sig --release 9 --sig core --hashed --clean-old-packages --full-run
# This assumes the directories already exist and will update in place. # This assumes the directories already exist and will update in place.
~/.local/bin/poetry run sync_sig --release 9 --sig core --hashed --clean-old-packages ~/.local/bin/poetry run sync-sig --release 9 --sig core --hashed --clean-old-packages
``` ```
## Syncing Composes ## Syncing Composes