-
Notifications
You must be signed in to change notification settings - Fork 2k
Use more descriptive long-form options for curl, tar, and checksum validation #6496
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is limited to the three commands you described. Are there plans to expand this everywhere? At a glance, I can see ln
and mkdir
as candidates. I guess what's the overall plan here?
Here's a HN post that describes much the same thing: https://news.ycombinator.com/item?id=43440184. It's useful context for folks (including us, later) who want to understand the motivation. |
Yes, I acknowledge that I left out |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other commands I see that can use long form are rm -rf
and useradd -l
.
- tdnf install - useradd - apt-get install - rm
OK, here's what I did:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This strikes a good balance of short and long form, I think.
(Markdown link check failure is a false positive) |
Reading through our Dockerfiles can be a little confusing if you're not familiar with specific command line option abbreviations for
curl
,tar
, etc.This PR attempts to make them easier to read by using the long-form options:
curl -fSLO
->curl --fail --silent --location --output
tar -oxzf
->tar --gzip --extract --no-same-owner --file
sha512sum -c ...
->sha512sum --check ...