On 2010-12-05 23:17, John H Palmieri wrote:
> On Dec 5, 2:00 pm, Jeroen Demeyer wrote:
>> On 2010-12-05 18:37, John H Palmieri wrote:
>>
>>> What's the difference? Right now we never call pipestatus with
>>> arguments in this form, do we?
>>
>> Actually we do in the "make build" rule:
>> $(PI
On Dec 5, 2:00 pm, Jeroen Demeyer wrote:
> On 2010-12-05 18:37, John H Palmieri wrote:
>
> > What's the difference? Right now we never call pipestatus with
> > arguments in this form, do we?
>
> Actually we do in the "make build" rule:
> $(PIPE) "cd spkg && ./install all 2>&1" "tee -a ../inst
On 2010-12-05 18:37, John H Palmieri wrote:
> What's the difference? Right now we never call pipestatus with
> arguments in this form, do we?
Actually we do in the "make build" rule:
$(PIPE) "cd spkg && ./install all 2>&1" "tee -a ../install.log"
So the question becomes: do we want to write
On Dec 5, 2:16 am, Jeroen Demeyer wrote:
> The command spkg/pipestatus runs two commands in a pipeline CMD1 | CMD2
> and returns the exit status of CMD1 if CMD1 fails but CMD2 is successful
> (normally, CMD1 | CMD2 would always exit with the status of CMD2). This
> is useful in Makefile where CMD
