From: Bernard Cafarelli <voyageur@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: gnustep-base.eclass
Date: Mon, 8 Oct 2007 00:43:45 +0200 [thread overview]
Message-ID: <20071008004345.62ab5a23@enterprise.cafarelli.fr> (raw)
In-Reply-To: <20071006000817.GQ29572@supernova>
Le Fri, 5 Oct 2007 17:08:17 -0700
Donnie Berkholz <dberkholz@gentoo.org> 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, ie.
> >
> > cat << \EOF > "${T}"/${cfile}
> >
> > or
> > cat << 'EOF' > "${T}"/${cfile}
> >
> > This turns off parameter and arithmetic expansion and command
> > substitution.
>
> That is so cool. Just another reason I love this reviewing.
Yes, thanks for the suggestion, this looks perfect!
These lines originally had some ${GNUSTEP_...} variables in them, which
required expansion in the ebuild, hence the backquotes forest...
Now, however the only one here is ${P}, which will probably be left
alone in its own echo command. I'll look into that soon.
By the way, even if this probably won't be need in that case, what's
the policy on adding files for eclasses, as uberlord suggested? The
only subfolder in eclasses/ for now is ELT-patches, but maybe because
for now no eclass needed that feature
--
Bernard Cafarelli (Voyageur)
NX and GNUstep Gentoo developer
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-10-07 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Idkm9-0003dm-4y@stork.gentoo.org>
2007-10-05 18:03 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: gnustep-base.eclass Donnie Berkholz
2007-10-05 18:12 ` Fabian Groffen
2007-10-05 18:50 ` George Shapovalov
2007-10-05 19:47 ` Roy Marples
2007-10-05 23:31 ` Ryan Hill
2007-10-06 0:08 ` Donnie Berkholz
2007-10-07 22:43 ` Bernard Cafarelli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071008004345.62ab5a23@enterprise.cafarelli.fr \
--to=voyageur@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox