On Mon, Mar 28, 2005 at 12:10:07PM -0600, Rob Browning wrote: > Marc Haber <[EMAIL PROTECTED]> writes: > > Stupid question: The commands you pipe into dpep end up being executed > > by the shell that is invoked by dpep in the editable source tree? > > Yes. The idea is to semi-automatically update our autofiles.dpatch. > Those commands run all the autofoo needed to bring the > dpatch-edit-patch temp tree up to date. I presume as far as the shell > that dpatch-edit-patch launches is concerned, all those commands are > just coming in over stdin, as if they'd been typed. > > Actually, as a possibly more flexible alternative, dpatch-edit-patch > could just allow multiple --command arguments and execute them in > order. If there were no --command arguments, the default would be > --command=/bin/sh, which would preserve the current behavior.
That would be a problem with getopt, which later versions of dpep use. > Of course with such an approach, it might be nicer if > dpatch-edit-patch treated any non-zero exit status as an abort, rather > than just exit 230, but I suppose you can always use shell traps to > work around that, at least if you're using scripts rather than > compiled executables for your --commands. > > Also, I'm not stuck on --command, --cmd, -c, or whatever would be > fine. Nice idea. A patch will be considered. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
