From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org, ali_bush@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: java-utils-2.eclass java-virtuals-2.eclass
Date: Thu, 4 Oct 2007 19:00:02 -0700 [thread overview]
Message-ID: <20071005020002.GB29572@supernova> (raw)
In-Reply-To: <E1IdNUP-00049g-MT@stork.gentoo.org>
On 09:59 Thu 04 Oct , Alistair Bush (ali_bush) wrote:
> 1.1 eclass/java-virtuals-2.eclass
>
> file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/java-virtuals-2.eclass?rev=1.1&view=markup
> plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/java-virtuals-2.eclass?rev=1.1&content-type=text/plain
> dodir "${JAVA_PKG_VIRTUALS_PATH}"
> if [[ -n "${JAVA_VIRTUAL_PROVIDES}" ]]; then
> echo "PROVIDERS=\"${JAVA_VIRTUAL_PROVIDES}\"" \
> >> ${JAVA_PKG_VIRTUAL_PROVIDER}
> fi
>
> if [[ -n "${JAVA_VIRTUAL_VM}" ]]; then
> echo "VM=\"${JAVA_VIRTUAL_VM}\"" \
> >> ${JAVA_PKG_VIRTUAL_PROVIDER}
> fi
>
> if [[ -n "${JAVA_VIRTUAL_VM_CLASSPATH}" ]]; then
> echo "VM_CLASSPATH=\"${JAVA_VIRTUAL_VM_CLASSPATH}\"" \
> >> ${JAVA_PKG_VIRTUAL_PROVIDER}
> fi
You can use a neat trick with a code block here, along these lines:
{
echo foo
echo bar
echo blah
} >> file
It avoids the possibility of a typo when you're retyping the same
filename multiple times, plus it's just cool.
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
next parent reply other threads:[~2007-10-05 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1IdNUP-00049g-MT@stork.gentoo.org>
2007-10-05 2:00 ` Donnie Berkholz [this message]
2007-10-05 8:51 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: java-utils-2.eclass java-virtuals-2.eclass Duncan
2007-10-05 11:14 ` Alistair Bush
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=20071005020002.GB29572@supernova \
--to=dberkholz@gentoo.org \
--cc=ali_bush@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