Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct wording for buildpack new targets flag #2296

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gogolok
Copy link

@gogolok gogolok commented Dec 2, 2024

Summary

I'm not a native speaker, but the output from
pack buildpack new
regarding the flag --targets confuses me. I hope my change/suggestion makes it more understandable.

Output

Before

Error: accepts 1 arg(s), received 0
Usage:
  pack buildpack new <id> [flags]

Examples:
pack buildpack new sample/my-buildpack

Flags:
  -a, --api string        Buildpack API compatibility of the generated buildpack (default "0.8")
  -h, --help              Help for 'new'
  -p, --path string       Path to generate the buildpack
  -t, --targets strings   Targets are the list platforms that one targeting, these are generated as part of scaffolding inside buildpack.toml file. one can provide target platforms in format [os][/arch][/variant]:[distroname@osversion@anotherversion];[distroname@osversion]
                          	- Base case for two different architectures :  '--targets "linux/amd64" --targets "linux/arm64"'
                          	- case for distribution version: '--targets "windows/amd64:[email protected]"'
                          	- case for different architecture with distributed versions : '--targets "linux/arm/v6:[email protected]"  --targets "linux/arm/v6:[email protected]"'

  -V, --version string    Version of the generated buildpack (default "1.0.0")

Global Flags:
      --force-color   Force color output
      --no-color      Disable color output
  -q, --quiet         Show less output
      --timestamps    Enable timestamps in output
  -v, --verbose       Show more output

After

Error: accepts 1 arg(s), received 0
Usage:
  pack buildpack new <id> [flags]

Examples:
pack buildpack new sample/my-buildpack

Flags:
  -a, --api string        Buildpack API compatibility of the generated buildpack (default "0.8")
  -h, --help              Help for 'new'
  -p, --path string       Path to generate the buildpack
  -t, --targets strings   Targets are the platforms that one targets. These are generated as part of scaffolding inside buildpack.toml file. One can provide target platforms in format [os][/arch][/variant]:[distroname@osversion@anotherversion];[distroname@osversion]
                          	- Base case for two different architectures :  '--targets "linux/amd64" --targets "linux/arm64"'
                          	- case for distribution version: '--targets "windows/amd64:[email protected]"'
                          	- case for different architecture with distributed versions : '--targets "linux/arm/v6:[email protected]"  --targets "linux/arm/v6:[email protected]"'

  -V, --version string    Version of the generated buildpack (default "1.0.0")

Global Flags:
      --force-color   Force color output
      --no-color      Disable color output
  -q, --quiet         Show less output
      --timestamps    Enable timestamps in output
  -v, --verbose       Show more output

Documentation

  • Should this change be documented?
    • Yes, see #___
    • No

@gogolok gogolok requested review from a team as code owners December 2, 2024 14:36
@gogolok gogolok changed the title Correct wording for buildpack new targerts flag Correct wording for buildpack new targets flag Dec 2, 2024
@github-actions github-actions bot added the type/enhancement Issue that requests a new feature or improvement. label Dec 2, 2024
@github-actions github-actions bot added this to the 0.37.0 milestone Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Issue that requests a new feature or improvement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant