#5 coreutils-single: upgrade coreutils-common Suggests to Recommends
Opened 3 years ago by cyberpear. Modified 3 years ago
rpms/ cyberpear/coreutils recommend-coreutils-common  into  master

No commits found

Mainly, this provides the convenience ll alias and other features of colorls.sh that are painful when missing. Adds 76K to a container, if installed (with typical tsflags=nodocs and %_install_langs C), but it's still optional via Recommends (not Requires) The existing Suggests is basically a no-op, telling libsolv to prefer coreutils-common over another package that fulfils the same dependencies, but does not indicate to actually install it.

# rpm -ql coreutils-common | sort -u | tac | xargs sh -c 'find "$@" -maxdepth 0 2>/dev/null' -- | xargs du -hcd0
36K /usr/share/licenses/coreutils-common/COPYING
8.0K    /usr/share/licenses/coreutils-common
4.0K    /etc/profile.d/colorls.sh
4.0K    /etc/profile.d/colorls.csh
8.0K    /etc/DIR_COLORS.lightbgcolor
8.0K    /etc/DIR_COLORS.256color
8.0K    /etc/DIR_COLORS
76K total

Well "Recommends" is a stronger relation than "Suggests", and will cause package managers to install it automatically. I'm not sure that's appropriate

Generally folks using the single package will have weak deps disabled anyway, but it's helpful to expose the hint...

Now I am confused. If you have weak deps disabled, would the proposed change make any difference for you?

My workflow is to temporarily enable weak deps to see which other packages "should" be installed with the current package, then decide whether I want them. DNF has no option to install "Suggests" nor a way to show them. It's a dep solving hint only.

It does not sound like a mainstream use case. Either you optimize for performance and comfort, in which case you install coreutils-full, or you optimize for minimal installation footprint, in which case you install coreutils-single. If you need something more custom, you need to customize it yourself (and the current packaging already supports it).

Metadata