Le Fri, 5 Oct 2007 17:08:17 -0700
Donnie Berkholz <[EMAIL PROTECTED]> a écrit:
> On 17:31 Fri 05 Oct , Ryan Hill wrote:
> > If there aren't any variables that you actually need expanded in the
> > script (i didn't see any but could have easily missed it), just escape
> > the termination marker
On 17:31 Fri 05 Oct , Ryan Hill wrote:
> If there aren't any variables that you actually need expanded in the
> script (i didn't see any but could have easily missed it), just escape
> the termination marker, ie.
>
> cat << \EOF > "${T}"/${cfile}
>
> or
> cat << 'EOF' > "${T}"/${cfile
Donnie Berkholz wrote:
> On 10:51 Fri 05 Oct , Bernard Cafarelli (voyageur) wrote:
>> 1.4 eclass/gnustep-base.eclass
>>
>> file :
>> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/gnustep-base.eclass?rev=1.4&view=markup
>> plain:
>> http://sources.gentoo.org/viewcvs.p
On Fri, 2007-10-05 at 11:03 -0700, Donnie Berkholz wrote:
> There's gotta be a better way of doing this. All those escapes really
> start to obfuscate the code. Anyone got a better idea?
Create a dir in eclasses to store proper files.
Then just copy it from there.
We store real patches in ELT-pa
Friday, 5. October 2007, Donnie Berkholz Ви написали:
> There's gotta be a better way of doing this. All those escapes really
> start to obfuscate the code. Anyone got a better idea?
Just use single quotes? This should prevent bash expansion.
Although, as I can see, this is done in here-function,
On 05-10-2007 11:03:56 -0700, Donnie Berkholz wrote:
> > - echo '#!/usr/bin/env bash' > "${T}"/${cfile}
> > - echo "echo Applying ${P} default configuration ..." >> "${T}"/${cfile}
> > + cat << EOF > "${T}"/${cfile}
> > +#!/usr/bin/env bash
> > +gnustep_append_default() {
> > + if [[ -z \$1
On 10:51 Fri 05 Oct , Bernard Cafarelli (voyageur) wrote:
> 1.4 eclass/gnustep-base.eclass
>
> file :
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/gnustep-base.eclass?rev=1.4&view=markup
> plain:
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/gnustep-ba
