Xyne wrote: >This may break simple scripts that naively parse the output (updaters, >notifiers, downloaders, ...). While that is not officially supported there is >really no reason to change expected behavior for this. I think a better >approach would be to omit ignored packages unless they are explicitly included >on the command line. Otherwise perhaps you could use a special argument to >'--ignore' (or a custom option) to stop ignoring packages for a given operation >(e.g. --ignore -). > >Both cases remain backwards compatible with past behavior and avoid surprises. > >Regards, >Xyne > >
Just to give a concrete example of how this applies, let's say that the user has ignored "foo". Running "pacman -Sp <group>" where foo is a member of <group> should not include foo in the output. It would also apply when printing groups that overlap with ignored groups. Allan McRae wrote: >I just realised that "pacman -Sp --ignore glibc glibc" makes little >sense, so just -Sup case then. In that case it doesn't, in others it does. Explicit "--ignore" options should override command-line arguments. For example, pacman -Sp --ignore foo $(pacman -Slq bar-repo) where foo is a member of [bar-repo]. Of course you can run the repo list through grep or some other filter, but it is logical to expect an "--ignore" option to force pacman to ignore a package and I think it would be consistent behavior.
