From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] DEFAULT_* proposal
Date: Sun, 09 Nov 2008 04:10:26 +0100 [thread overview]
Message-ID: <491654A2.9020908@gentoo.org> (raw)
In-Reply-To: <20081108222051.GA7464@spoc>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Thomas Anderson schrieb:
> src_install:
> All I want changed here is a variable for a list of extra docs to be
> installed. This'll require a default function for
> src_install and I propose:
> src_install() {
> emake -j1 install DESTDIR="${D}" || die "make install died"
> [[ -n ${DEFAULT_SRC_INSTALL_DOCS} ]] && dodoc \
> ${DEFAULT_SRC_INSTALL_DOCS}
> }
> bug #33544 has more information on this topic, as does
> tommy's recent thread on the subject of default src_install
> function.
At least for this one, why dont you use my proposal?
-default should always be unlimited emake, so no -j1
-Why die, if emake fails because of missing makefile (as meta ebuilds tend to have)?
-Why not check for some default docs and install them if they exist and make dodoc die on error?
this is at least, what my latest proposal does:
src_install() {
if [ -f Makefile ] || [ -f GNUmakefile ] || [ -f makefile ]; then
emake DESTDIR="${D}" install || die "emake install failed"
fi
if [ -n "${DOCS}" ]; then
dodoc ${DOCS} || die "dodoc failed"
else
for x in AUTHORS ChangeLog NEWS README; do
if [ -e ${x} ]; then
dodoc ${x} || die "dodoc ${x} failed"
fi
done
fi
}
The rest of the proposal looks acceptable to me.
--
Thomas Sachau
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 315 bytes --]
next prev parent reply other threads:[~2008-11-09 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 22:20 [gentoo-dev] DEFAULT_* proposal Thomas Anderson
2008-11-09 3:10 ` Thomas Sachau [this message]
2008-11-09 12:39 ` Peter Volkov
2008-11-09 14:04 ` Thomas Anderson
2008-11-09 15:28 ` Peter Volkov
2008-11-09 15:02 ` Santiago M. Mola
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=491654A2.9020908@gentoo.org \
--to=tommy@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