[pacman-dev] command line arguments

Xavier shiningxc at gmail.com
Sat Sep 29 08:11:54 EDT 2007

On Sat, Sep 29, 2007 at 01:48:29PM +0200, Nagy Gabor wrote:
> A bit off in this thread, but the current command-line handling of pacman is
> chaotic, for example the bahaviour of -Quil is not defined. We should
> restructure a bit, we should categorize options: (my example assumes -S)
> -operation: -l, -i, -c, -l, -p, -s, -y ... <- more than one allowed (pacman try
> to do all requested operations)
> -loadtarget/targettype-modifier options, -g, (--provider), -u (!!) ... <- only
> one allowed
> -trans_prepare/new-target-pull options: -d, (--noconflict option), -e ... <-
> more than one allowed
> -trans_commit options: -f, --asdeps, -w (do nothing) ... <- more than one allowed
> As an example, I explain what should pacman -Quetcl do:
> List all explicitly installed outdated not-a-dependency-of-other packages and
> show their changlogs and filelists ;-)

I think that's a good idea, but a lot of work again :)

More information about the pacman-dev mailing list