[Yum-devel] [PATCH 2/2] Add documentation for assumeyes change.
james at fedoraproject.org
Mon Jul 11 18:40:11 UTC 2011
On Mon, 2011-07-11 at 19:05 +0200, tim.lauridsen at gmail.com wrote:
> Do we really need all these cases ?
> I can see the use for -y for installing/updating stuff, but not
> removing stuff. but having options for all possible combination seams
> like overkill for me and it make the code very complex and hard to
I've been thinking about this for a few days, and eventually just
decided to try something, as Seth wanted basically:
allow me to do '''yum remove blah\*''', but only if there are no deps.
being removed too"
...which, in theory, just means removing the checked for "is removal"
maybe-and the checks for "txmbr.name in extcmds". The problem is that
doing this "minimal" change means that remove and install are toggled by
the same switch ... where seems unlikely to be desired by everyone, and
means there's no good way to be backwards compatible with current
At the other end, I could see people wanting to distinguish between
deps. on upgrade vs. deps. on removals ... and even things like local
packages, or clean_requirements_on_remove deps.
In the end I thought I'd go for listing the types of txmbr, the two old
tests and added in the three options for skip-broken and load-ts ...
then I could see what everyone thought?
So would you use it, if we just removed the "txmbr.ts_state == 'e'"
part of the conditional? Any other thoughts on how we could change it to
More information about the Yum-devel