From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New eclass: go-mono.eclass
Date: Sun, 18 Jan 2009 19:02:10 -0800 [thread overview]
Message-ID: <20090119030209.GB3562@comet> (raw)
In-Reply-To: <200901162103.27740.loki_val@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On 21:03 Fri 16 Jan , Peter Alfredsen wrote:
> NO_MONO_DEPEND=(
> "dev-lang/mono"
> "dev-dotnet/libgdiplus"
> "dev-dotnet/gluezilla"
> )
I'm not a huge fan of having package-specific logic in eclasses. This
would be nicer to see as a variable set in the packages like
MONO_DEPEND="no". That would also get rid of the double-negative logic
below:
> if ! has "${CATEGORY}/${PN}" "${NO_MONO_DEPEND[@]}"
> then
> RDEPEND="=dev-lang/mono-${GO_MONO_REL_PV}*"
> DEPEND="${RDEPEND}"
> fi
> if [[ "${PV%_rc*}" != "${PV}" ]]
> then
> GO_MONO_P="${P%_rc*}"
> SRC_URI="${PRE_URI}/${PN}/${GO_MONO_P} -> ${P}.tar.bz2"
> S="${WORKDIR}/${GO_MONO_P}"
> elif [[ "${PV%_pre*}" != "${PV}" ]]
> then
> GO_MONO_P="${P%_pre*}"
> SRC_URI="${PRE_URI}/${PN}/${GO_MONO_P} -> ${P}.tar.bz2"
> S="${WORKDIR}/${GO_MONO_P}"
> else
> GO_MONO_P=${P}
> SRC_URI="http://ftp.novell.com/pub/mono/sources/${PN}/${P}.tar.bz2"
> fi
How about GO_MONO_P=${P%_[a-z]*} -- doesn't that work in all cases?
--
Thanks,
Donnie
Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-01-19 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 20:03 [gentoo-dev] New eclass: go-mono.eclass Peter Alfredsen
2009-01-17 12:04 ` Petteri Räty
2009-01-17 12:41 ` Peter Alfredsen
2009-01-17 13:31 ` Peter Volkov
2009-01-17 13:48 ` Peter Alfredsen
2009-01-19 3:02 ` 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=20090119030209.GB3562@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