From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [PATCH 1/2] elisp-common.eclass: Some functions now die on failure.
Date: Fri, 8 Mar 2013 20:57:43 +0100 [thread overview]
Message-ID: <20794.17079.866829.303673@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20794.16989.965476.563290@a1i15.kph.uni-mainz.de>
* elisp-common.eclass (elisp-compile, elisp-make-autoload-file)
(elisp-install, elisp-site-file-install): Die on failure.
* elisp.eclass (elisp_src_compile, elisp_src_install): Remove die
commands that are no longer necessary because the called functions
die themselves.
--- a/eclass/elisp-common.eclass
+++ b/eclass/elisp-common.eclass
@@ -50,7 +50,7 @@
# directory is added to the load-path which makes sure that all files
# are loadable.
#
-# elisp-compile *.el || die
+# elisp-compile *.el
#
# Function elisp-make-autoload-file() can be used to generate a file
# with autoload definitions for the lisp functions. It takes the output
@@ -70,7 +70,7 @@
# choose something else, but remember to tell elisp-site-file-install()
# (see below) the change, as it defaults to ${PN}.
#
-# elisp-install ${PN} *.el *.elc || die
+# elisp-install ${PN} *.el *.elc
#
# To let the Emacs support be activated by Emacs on startup, you need
# to provide a site file (shipped in ${FILESDIR}) which contains the
@@ -112,7 +112,7 @@
#
# Which is then installed by
#
-# elisp-site-file-install "${FILESDIR}/${SITEFILE}" || die
+# elisp-site-file-install "${FILESDIR}/${SITEFILE}"
#
# in src_install(). Any characters after the "-gentoo" part and before
# the extension will be stripped from the destination file's name.
@@ -168,6 +168,7 @@ EMACSFLAGS="-batch -q --no-site-file"
BYTECOMPFLAGS="-L ."
# @FUNCTION: elisp-emacs-version
+# @RETURN: exit status of Emacs
# @DESCRIPTION:
# Output version of currently active Emacs.
@@ -223,7 +224,7 @@ elisp-need-emacs() {
elisp-compile() {
ebegin "Compiling GNU Emacs Elisp files"
${EMACS} ${EMACSFLAGS} ${BYTECOMPFLAGS} -f batch-byte-compile "$@"
- eend $? "elisp-compile: batch-byte-compile failed"
+ eend $? "elisp-compile: batch-byte-compile failed" || die
}
# @FUNCTION: elisp-make-autoload-file
@@ -259,7 +260,7 @@ elisp-make-autoload-file() {
--eval "(setq generated-autoload-file (expand-file-name \"${f}\"))" \
-f batch-update-autoloads "${@-.}"
- eend $? "elisp-make-autoload-file: batch-update-autoloads failed"
+ eend $? "elisp-make-autoload-file: batch-update-autoloads failed" || die
}
# @FUNCTION: elisp-install
@@ -275,7 +276,7 @@ elisp-install() {
insinto "${SITELISP}/${subdir}"
doins "$@"
)
- eend $? "elisp-install: doins failed"
+ eend $? "elisp-install: doins failed" || die
}
# @FUNCTION: elisp-site-file-install
@@ -305,7 +306,7 @@ elisp-site-file-install() {
)
ret=$?
rm -f "${sf}"
- eend ${ret} "elisp-site-file-install: doins failed"
+ eend ${ret} "elisp-site-file-install: doins failed" || die
}
# @FUNCTION: elisp-site-regen
--- a/eclass/elisp.eclass
+++ b/eclass/elisp.eclass
@@ -151,7 +151,7 @@ elisp_src_configure() { :; }
# GNU Info files from them.
elisp_src_compile() {
- elisp-compile *.el || die
+ elisp-compile *.el
if [[ -n ${ELISP_TEXINFO} ]]; then
makeinfo ${ELISP_TEXINFO} || die
fi
@@ -165,9 +165,9 @@ elisp_src_compile() {
# ELISP_TEXINFO and documentation listed in the DOCS variable.
elisp_src_install() {
- elisp-install ${PN} *.el *.elc || die
+ elisp-install ${PN} *.el *.elc
if [[ -n ${SITEFILE} ]]; then
- elisp-site-file-install "${FILESDIR}/${SITEFILE}" || die
+ elisp-site-file-install "${FILESDIR}/${SITEFILE}"
fi
if [[ -n ${ELISP_TEXINFO} ]]; then
set -- ${ELISP_TEXINFO}
next prev parent reply other threads:[~2013-03-08 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 19:56 [gentoo-dev] Two updates for elisp*.eclass Ulrich Mueller
2013-03-08 19:57 ` Ulrich Mueller [this message]
2013-03-08 19:58 ` [gentoo-dev] [PATCH 2/2] elisp.eclass: Cooperate with readme.gentoo.eclass Ulrich Mueller
2013-03-08 20:02 ` [gentoo-dev] Two updates for elisp*.eclass Michał Górny
2013-03-08 20:31 ` Ulrich Mueller
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=20794.17079.866829.303673@a1i15.kph.uni-mainz.de \
--to=ulm@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