[pacman-dev] [PATCH] New Rg option
ngaba at bibl.u-szeged.hu
Tue Sep 18 08:38:40 EDT 2007
Idézés Xavier <shiningxc at gmail.com>:
> On Tue, Sep 18, 2007 at 02:24:24PM +0200, Nagy Gabor wrote:
> > > On Tue, Sep 18, 2007 at 02:00:24PM +0200, Nagy Gabor wrote:
> > > > > +1 on making -g work both for -S and -R.
> > > > >
> > > > > However, why don't we do the following for backwards compatability:
> > > > > 1. pacman -S grppkg: look for a package named grppkg, then group
> > > > > 2. pacman -Sg grppkg: look for a group named grppkg (and ignore a
> > > > > package if there is one)
> > > > > 3. pacman -R grppkg: only remove a package named grppkg (I don't
> > > > > group removal is used enough to warrant keeping backwards compat)
> > > > > 4. pacman -Rg grppkg: remove a group named grppkg
> > > > IMHO that would be a bit confusing. And differentiate between group
> > > package
> > > > install would help to keep the code clean.
> > > >
> > >
> > > Which part exactly is confusing?
> > I understand Dan's idea, but
> > 1. I don't like "undeterministic" things, so if I (or crond ;-) do a
> "pacman -Sy
> > favgrp", I want to do a group install independent from the current state of
> > repos (today pacman may install a group, tomorrow pacman may install a
> > 2. Why should I do "pacman -S favgrp", when I can do "pacman -Sg favgrp"?
> > 3. Personally, I didn't like the current method either (pacman -S group).
> Just so we're clear, it's only the backward compatibility of 1. that you
> like, right?
Of course, sorry, if I wasn't clear.
+1 for -Sg and -Rg
SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu
This mail sent through IMP: http://horde.org/imp/
More information about the pacman-dev