`--accept-source-agreements ` (and the package equivalent) documentation is insufficient

Brief description of your issue

These flags' behaviour could be better described. For the source, it is probably sufficient, but esp for package agreements (if I interpret that correctly to begin with), more elaboration should be given. Specifically, how it behaves for:

• "just a EULA" (this is simple, and if users knew it only applied to EULAs, that should be stated, and no further changes would be needed
• "optional flags in installers" (many offer to install extra stuff in a single installer, like optional components in the nvidia GPU driver, or git for windows extras)
• "whole extra software packages" (if someone offers extra software as an ad, like how many antivirus programs pay to get a hey do you want this too box in installers for various things)
• any other stuff i can't think of rn that may be material?

Should be fairly easy, anyone familiar w/ these features should be able to add that clarity, so users can make an informed choice to use them or not.

TIA

Locate the documentation for the --accept-source-agreements flag and its package equivalent, then review how source and package agreements are described. Clarify the behavior for EULAs, optional installer components, extra software offers, and other material agreements so users can make an informed choice.