Re: use of {} shell wildcards in debian/rules

2005-09-02 Thread Steve Langasek
Please fix your broken From: header. On Fri, Sep 02, 2005 at 05:44:26PM +0300, Delian Delchev wrote: > Jeroen van Wolffelaar wrote: > >On Fri, Sep 02, 2005 at 03:17:30PM +0100, Toby White wrote: > >>Since they are Makefiles, there is no convention (is there?) for specifying > >>which shell shoul

Re: use of {} shell wildcards in debian/rules

2005-09-02 Thread Delian Delchev
Jeroen van Wolffelaar wrote: >On Fri, Sep 02, 2005 at 03:17:30PM +0100, Toby White wrote: > > >>Since they are Makefiles, there is no convention (is there?) for specifying >>which shell should be used to execute commands. >> >> > >I use "export SHELL=/bin/bash" in the top of Makefiles where

Re: use of {} shell wildcards in debian/rules

2005-09-02 Thread Colin Watson
On Fri, Sep 02, 2005 at 03:17:30PM +0100, Toby White wrote: > I have recently come across this behaviour while rebuilding > modxslt; in the debian/rules file, there are several instances > of the idiom: > > @cp -a $(CURDIR)/debian/libmodxslt0/usr/lib/libmodxslt0{.a,.la} \ >$(CURDIR)/debian

Re: use of {} shell wildcards in debian/rules

2005-09-02 Thread Jeroen van Wolffelaar
On Fri, Sep 02, 2005 at 03:17:30PM +0100, Toby White wrote: > Since they are Makefiles, there is no convention (is there?) for specifying > which shell should be used to execute commands. I use "export SHELL=/bin/bash" in the top of Makefiles where I use bashisms. I greatly prefer that over making