Some further thoughts:
But if nearly everything gets the same label I think it looses it's meaning or value - just like adding a "software" label to all programs, while that is true, it is not very helpful to the user and the label doesn't stand out.
An alternative might be to swap the tags around. I don't think pandoc, youtube-dl and others are a "package" - they are just programs you can use to do something - either consisting of one or more other files needed to make it work and you need to figure out how to download, install and use them by reading the documentation - either here on TPFC or on the programs website. A bit more work is to be expected when dealing with CLI.
Example:
Yori or ImageMagick are a "collection" but all the programs that come with them are "part of" the collection are a "package". You can't download and use
WinPos as an individual program to move windows as you need to do get something else first like installing Yori or extracting a specific file from an installer/zip like convert.exe from ImageMagick.
So having a "part of" or "package" label with WinPos might be more meaningful to someone searching and browsing the CLI section who is trying to find a solution for: I'm looking for a tool to move windows. The answers could be:
NirCmd - not a package: yes - I can download and use that directly (one program I can call from my batch file or other situation) - easy to update probably by downloading a new version.
WinPos - package: no - I can't because I would need to install Yori first, copy the WinPos program and only after that use it just to be able to move a window to automate my workflow. And when there is an update do it again.
Or
- omit "package" and introduce a label to indicate it is "not a standalone application you can use directly"
- avoid individual entries for "WinPos" et al all together (I know that is discussed already, I don't have an opinion on it)
But in the end the fact an entry is there is probably more helpful than having any sort of labels.
