[pacman-dev] command line arguments

Aaron Griffin aaronmgriffin at gmail.com
Mon Oct 1 15:53:26 EDT 2007

On 9/29/07, Xavier <shiningxc at gmail.com> wrote:
> 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 :)

It's always "a lot of work". C'est la vie.

This is why Dan and I like to harp on people for patches. We're just
two guys, and we both have full time jobs (ok, I now have a second job
if you look at the main Arch page) and social lives.

It's hard to do everything everyone wants.

That's also why I love when people run their own git branches. I don't
have to do much extra. I remote update and voila! I have all your work
to import.

It's amazing.

Keep up good the work guys.

More information about the pacman-dev mailing list