From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: emboss.eclass as replacement for embassy.eclass
Date: Tue, 15 Mar 2011 18:06:36 -0400 [thread overview]
Message-ID: <201103151806.36778.vapier@gentoo.org> (raw)
In-Reply-To: <4D7FD134.4060606@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 4292 bytes --]
> # Copyright 1999-2004 Gentoo Foundation
s/2004/2011/
have you looked at the man page output for this to make sure the white spacing
you're putting into the comments properly carries over ?
> # @ECLASS-VARIABLE: EBO_DESCRIPTION
> # @DESCRIPTION:
> # Should be set. Completes the describtion of the embassy module as follows:
i dont understand what this is trying to say (ignoring the spelling mistake in
description)
> # EMBOSS integrated version of EBO_DESCRIPTION"
i see just one quote. it needs a friend.
> # @ECLASS-VARIABLE: EBO_PATCH
> # @DEFAULT_UNSET
> # @DESCRIPTION: Specify the patch level of EMBOSS. Only available for the
emboss ebuild.
> # The patch wil be fetch from:
wil -> will
> # @ECLASS-VARIABLE: NO_RECONF
> # @DEFAULT_UNSET
> # @DESCRIPTION:
> # Set this, if you do not want to have eautoreconf be run after patching.
please namespace all variables consistently
> # @ECLASS-VARIABLE: EBO_ECONF
EBO_EXTRA_ECONF is better for consistency sake too
> EAPI="4"
erp!
> HOMEPAGE="http://emboss.sourceforge.net"
could do with a trailing "/"
> IUSE="mysql pdf png postgres static-libs X "
no trailing space. let the person appending the variable add the space:
IUSE+=" moo"
> DOCS="AUTHORS ChangeLog NEWS README "
no need for that trailing space, and usually DOCS is left for end ebuilds isnt
it ? eclasses should append it.
>
> if [[ ${PN} == "emboss" ]] ; then
> EBOV=${PV/_p*}
> DESCRIPTION="The European Molecular Biology Open Software Suite - A
sequence analysis package"
> SRC_URI="ftp://emboss.open-bio.org/pub/EMBOSS/EMBOSS-${EBOV}.tar.gz"
> [[ -n ${EBO_PATCH} ]] && SRC_URI+=" ftp://${PN}.open-
bio.org/pub/EMBOSS/fixes/patches/patch-1-${EBO_PATCH}.gz -> ${P}.patch.gz"
> IUSE+="minimal "
> RDEPEND+="
> !sys-devel/cons
> "
> PDEPEND+="
> !minimal? (
> sci-biology/aaindex
> sci-biology/cutg
> sci-biology/prints
> sci-biology/prosite
> sci-biology/rebase
> sci-biology/transfac
> )
> "
> S=${WORKDIR}/EMBOSS-${EBOV}
> DOCS+="FAQ THANKS "
this doesnt make much sense to me. shouldnt this all be in the emboss ebuild
instead of the eclass ?
> # The EMBASSY package name, retrieved from the inheriting ebuild's name
> EN=${PN:8}
should there be some checking here to make sure it starts with "embassy-" or
whatever you're expecting ?
> # The full name and version of the EMBASSY package (excluding the Gentoo
> # revision number)
> EF=$(echo ${EN} | tr "[:lower:]" "[:upper:]")-${PV}
ugh, but i guess we cant do much until we have newer bash
> EBO_DESCRIPTION=${EBO_DESCRIPTION:=${EN}}
tricky, but wrong. i guess you actually want:
: ${EBO_DESCRIPTION:=${EN}}
> DEPEND+=">=sci-biology/emboss-6.3.1_p4[mysql=,pdf=,png=,postgres=,static-
libs=,X=] "
space should be at the start of the string, not the end
> # @FUNCTION: emboss_src_prepare
> # @USAGE:
> # @RETURN:
> # @MAINTAINER:
i dont think these three tags make sense. not even sure if this last one is
even allowed. best to just punt.
same goes for all the other funcs below.
> emboss_src_prepare() {
> [[ ${PN} == emboss ]] && [[ -n ${EBO_PATCH} ]] && epatch
"${WORKDIR}"/${P}.patch
guess that would be moved to the emboss ebuild
> [[ -f "${FILESDIR}"/${PF}.patch ]] && epatch "${FILESDIR}"/${PF}.patch
technically, no need to quote FILESDIR here as the [[...]] takes care of it
> # $(use_with png pngdriver "${EPREFIX}/usr")
> # $(use_with pdf hpdf "${EPREFIX}/usr")
> # $(use_with mysql mysql "${EPREFIX}/usr/bin/mysql_config")
> # $(use_with postgres postgresql "${EPREFIX}/usr/bin/pg_config")
do you really need full paths here ? are the configure scripts that screwed
up ? ideally libs would be found via .pc files.
> # $(use_enable amd64 64)
oh god it burns so bad when i poo
> emboss_src_install() {
> default
> mv "${ED}"/usr/share/EMBOSS/doc/* "${ED}"/usr/share/doc/${PF}/
> rm -rf "${ED}"/usr/share/EMBOSS/doc
does the configure script respect --docdir= ? then you wouldnt need this
clean up logic ...
> [[ ${PN} == embassy ]] || EXPORT_FUNCTIONS src_prepare src_configure
src_install
this $PN logic should get punted
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-03-15 22:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 7:33 [gentoo-dev] RFC: emboss.eclass as replacement for embassy.eclass justin
2011-03-15 20:51 ` justin
2011-03-15 21:25 ` Tomáš Chvátal
2011-03-16 6:48 ` justin
2011-03-16 9:36 ` Tomáš Chvátal
2011-03-16 18:51 ` Mike Frysinger
2011-03-19 19:33 ` justin
2011-03-20 18:39 ` Mike Frysinger
2011-03-21 10:37 ` justin
2011-03-21 13:04 ` Mike Frysinger
2011-03-21 13:14 ` Fabian Groffen
2011-03-21 13:20 ` Mike Frysinger
2011-03-27 14:34 ` justin
2011-03-27 14:50 ` Mike Frysinger
2011-03-27 15:34 ` justin
2011-03-15 22:06 ` Mike Frysinger [this message]
2011-03-15 23:25 ` [gentoo-dev] " Duncan
2011-03-16 3:00 ` [gentoo-dev] " Jeroen Roovers
2011-03-16 3:17 ` Jeremy Olexa
2011-03-16 7:02 ` justin
2011-03-16 17:13 ` Jeroen Roovers
2011-03-16 17:59 ` Ulrich Mueller
2011-03-16 19:23 ` justin
2011-03-16 18:49 ` Mike Frysinger
2011-03-16 19:25 ` justin
2011-03-16 7:20 ` justin
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=201103151806.36778.vapier@gentoo.org \
--to=vapier@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