From: Angelo Arrifano <miknix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: betelgeuse@gentoo.org
Subject: Re: [gentoo-dev] Announcement of The G Palmtop Environment ebuilds
Date: Wed, 04 Feb 2009 14:03:27 +0000 [thread overview]
Message-ID: <1233756207.22368.29.camel@localhost> (raw)
In-Reply-To: <4989827F.3000907@gentoo.org>
On Qua, 2009-02-04 at 13:56 +0200, Petteri Räty wrote:
> Angelo Arrifano wrote:
> >
> > Since we are maintaining this over half a year now, we think that its
> > time to finally starting moving step-by-step the GPE suite into the
> > portage tree - starting with the eclass and toplevel categories.
> >
>
> Please start by posting the new eclasses for review then.
>
> Regards,
> Petteri
>
# Copyright 2008 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
#
# Authors:
# Rene Wagner <rw@handhelds.org>
# Ned Ludd <solar@gentoo.org>
# Angelo Arrifano <miknix@gentoo.org>
# based on gnome2.eclass and gpe.bbclass (the latter from OpenEmbedded)
inherit libtool toolchain-funcs
# GPE ECLASS
#GPECONF="" # extra configure opts passed to econf
ELTCONF="" # extra options passed to elibtoolize
DOCS="" # documentation files to be installed with dodoc
[ -z "${GPE_MIRROR}" ] && export GPE_MIRROR="http://gpe.linuxtogo.org/download/source"
[ -z "${GPE_TARBALL_SUFFIX}" ] && export GPE_TARBALL_SUFFIX="gz"
SRC_URI="${GPE_MIRROR}/${PN}-${PV}.tar.${GPE_TARBALL_SUFFIX}"
HOMEPAGE="http://gpe.handhelds.org/"
IUSE="${IUSE} nls"
GPECONF="${GPECONF} --enable-debug=no --disable-debug"
RDEPEND=""
DEPEND=">=dev-util/intltool-0.29 >=dev-util/pkgconfig-0.12.0"
gpe_src_configure() {
tc-export CC
if [ -f configure ]; then
elibtoolize ${ELTCONF}
econf "$@" ${GPECONF} || die "./configure failure"
fi
}
gpe_src_compile() {
tc-export CC
has "${EAPI:-0}" 0 1 && gpe_src_configure "$@"
emake PREFIX=/usr || die "compile failure"
}
gpe_src_install() {
USE_NLS=yes
use nls || USE_NLS=no
if [ -f configure ]; then
einstall "$@"
else
make DESTDIR=${D} PREFIX=/usr \
STRIP=true ENABLE_NLS=${USE_NLS} \
"$@" install
fi
# manual document installation
[ -n "${DOCS}" ] && dodoc ${DOCS}
}
gpe_src_unpack() {
unpack ${A}
cd "${S}"
# let portage handle stripping.
for x in $(find "${S}" -name 'Makefile*') ; do
sed -i -e s/'install -s'/'install'/g \
-e s/'install -Ds'/'install -D'/g \
-e 's/$(INSTALL) -s/$(INSTALL) /g' $x
done
}
EXPORT_FUNCTIONS src_compile src_install src_unpack
next prev parent reply other threads:[~2009-02-04 15:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 15:34 [gentoo-dev] Announcement of The G Palmtop Environment ebuilds Angelo Arrifano
2009-02-03 16:28 ` Richard Freeman
2009-02-03 17:10 ` Angelo Arrifano
2009-02-03 18:48 ` Ned Ludd
2009-02-03 18:54 ` Richard Freeman
2009-02-03 19:24 ` Donnie Berkholz
2009-02-03 19:47 ` Donnie Berkholz
2009-02-03 20:13 ` Angelo Arrifano
2009-02-03 20:20 ` Ciaran McCreesh
2009-02-03 21:37 ` [gentoo-dev] " Duncan
2009-02-04 11:56 ` [gentoo-dev] " Petteri Räty
2009-02-04 14:03 ` Angelo Arrifano [this message]
2009-02-04 16:36 ` Petteri Räty
2009-02-05 0:37 ` Angelo Arrifano
2009-02-05 0:51 ` Ned Ludd
2009-02-05 0:52 ` Petteri Räty
2009-02-07 21:05 ` Angelo Arrifano
2009-02-08 21:38 ` Petteri Räty
2009-02-05 20:21 ` [gentoo-dev] " Ryan Hill
2009-02-05 21:17 ` Petteri Räty
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=1233756207.22368.29.camel@localhost \
--to=miknix@gentoo.org \
--cc=betelgeuse@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