Re: dselect woes
dmacdoug@hsc.usc.edu wrote:
>
> Can it be! CAN IT BE!!
>
> Am I a complete idiot or is Deselect one of the most diabolical
>
> programs ever?
>
> It's so seductive. I've used it quite a number of times. Worked
>
> beautifully. Then I made a mistake. And each step to try to undo the
>
> mistake just digs the hole deeper. I'll never get out!
>
> Is it true that you can spend hours going through and selecting certain
>
> packages for installation and then, innocently select a package that
>
> happens to conflict with some other important package which is a
>
> required package for about a hundred or two other packages, and so, in
>
> a flash, dselect goes through and deslects all your tediously chosen
>
> packages without even giving you the option to say "oops I didn't
>
> really mean that?" Surely there's a way to back out of such an
>
> innocent mistake without having to go back through that whole list and
>
> reselect everything? I've looked at the man file and at the --help
>
> option and at whatever other documentation I could find, but don't see
>
> anything to help with this. I've just wasted hours, and what's worse, I
>
> don't know how to avoid the same pitfall in the future.
>
> Surely it cannot be!
>
> Donald MacDougall
When you got to the conflict/resolution screen after selecting
that package which conflicted with the other one, you should have
backed out of a screen like that with 'X' (shift-x; this is on the
help screen). This is essentially an 'escape' function. It would
have returned you to the package selection screen as if nothing
had been selected. Once you have exited a conflict/resolution
screen using anything other than 'X' you are stuck with the
results. Sorry, from now on be *very* careful in
conflict/resolution screens. Dselect makes most updates/upgrades
easy, but in conflicts, you have to pay attention.
--
Ed C.
Reply to: