You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's the groff weak dependency that adds all these additional packages. This is needed for formatting the help output supported by the CLI. You can avoid installing it by leaving out weak dependencies, e.g. with dnf install awscli-2 --setopt=install_weak_deps=False. The tradeoff is that help no longer works:
bash-5.2# aws help
Could not find executable named "groff or mandoc"
bash-5.2# aws ec2 help
Could not find executable named "groff or mandoc"
So, I believe that things are, in fact, working as expected. groff is not strictly needed, which is why it's a weak dependency, but it's convenient, which is why it's installed by default.
In theory we could consider an alternate configuration for the container images in general that does not install weak dependencies by default, but I think that would be too big a surprise for most people. The container image should generally behave like any other Amazon Linux installation.
It's the groff weak dependency that adds all these additional packages. This is needed for formatting the help output supported by the CLI. You can avoid installing it by leaving out weak dependencies, e.g. with dnf install awscli-2 --setopt=install_weak_deps=False. The tradeoff is that help no longer works:
bash-5.2# aws help
Could not find executable named "groff or mandoc"
bash-5.2# aws ec2 help
Could not find executable named "groff or mandoc"
So, I believe that things are, in fact, working as expected. groff is not strictly needed, which is why it's a weak dependency, but it's convenient, which is why it's installed by default.
In theory we could consider an alternate configuration for the container images in general that does not install weak dependencies by default, but I think that would be too big a surprise for most people. The container image should generally behave like any other Amazon Linux installation.
Describe the bug
Installing
AWS CLI2
in theAmazon Linux 2023 Minimal Container image
installs the following packages:Details
Does AWS CLI2 really have that many dependencies? Is this working as intended?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Not entirely sure, maybe less packages? According to the AWS CLI devs "
perl-* packages are not related to the AWS CLI
"Screenshots
-
Desktop (please complete the following information):
Amazon Linux 2023 Minimal Container image
Smartphone (please complete the following information):
-
Additional context
Related to aws/aws-cli#8317
The text was updated successfully, but these errors were encountered: