On Thu, March 22, 2007 5:50 pm, Lan Barnes wrote: > > On Thu, March 22, 2007 2:08 pm, John Oliver wrote: >> On Thu, Mar 22, 2007 at 01:51:35PM -0700, James G. Sack (jim) wrote: >>> >>> It appears that you didn't grasp the significance of what Greg said >>> about the '&&' separating your commands. >>> >>> If you want to: >>> try A, and then if that works try B, and then if that works try C >>> use >>> A && >>> B && >>> C >>> if you want to: >>> try A, and then (always) try B, and then (always) try C >>> use >>> A >>> B >>> C >> >> Ahhh! >> >> I thought the && would just move on to the next command after the >> completion, not necessarily the successful completion, of the first >> command. And that's what I want... I want it to try to install libgcc >> first, and only after that's complete, one way or the other, to move on >> to the next RPM command. >>
I think what you want is a semicolon: $do_me ; then_do_me >> I need to look up bash characters :-) >> me too :-( -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
