From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: new gnustep eclasses
Date: Mon, 6 Aug 2007 15:21:22 -0700 [thread overview]
Message-ID: <20070806222122.GA27510@comet> (raw)
In-Reply-To: <20070807000413.22d7849d@enterprise.cafarelli.fr>
On 00:04 Tue 07 Aug , Bernard Cafarelli wrote:
> Latest version of the base eclass (sent with this mail) can be found at:
> http://overlays.gentoo.org/proj/gnustep/browser/overlay/eclass/gnustep-base.eclass
>
> This one does most of the hard work, especially in egnustep_env which
> sets up an appropriate GNUstep compilation environment from the
> installed gnustep-make.
Some suggestions on the eclass ...
Instead of your eval trick, try something like what's in molden-4.6.ebuild:
typeset -a args
args=( CC="$(tc-getCC) ${CFLAGS}" \
FC="${FORTRANC}" LDR="${FORTRANC}" FFLAGS="${FFLAGS}" )
emake -j1 "${args[@]}" || die "molden emake failed"
Some of your die() calls lack messages. Please add them.
I like a little different setup for this type of function:
117 egnustep_make() {
118 if [ -f ./[mM]akefile -o -f ./GNUmakefile ] ; then
119 eval emake ${*} ${__GS_MAKE_EVAL} all || die "package make failed"
120 else
121 die "no Makefile found"
122 fi
123 }
Instead...
117 egnustep_make() {
118 if [ -f ./[mM]akefile -o -f ./GNUmakefile ] ; then
119 eval emake ${*} ${__GS_MAKE_EVAL} all || die "package make failed"
120 return 0
121 fi
122 die "no Makefile found"
123 }
But that's just a matter of preference. Same kinda deal for egnustep_install().
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-08-06 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 22:04 [gentoo-dev] RFC: new gnustep eclasses Bernard Cafarelli
2007-08-06 22:21 ` Donnie Berkholz [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=20070806222122.GA27510@comet \
--to=dberkholz@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