From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Two updates for elisp*.eclass
Date: Fri, 8 Mar 2013 20:56:13 +0100 [thread overview]
Message-ID: <20794.16989.965476.563290@a1i15.kph.uni-mainz.de> (raw)
Hi,
Please find in the next messages two patches for elisp.eclass and
elisp-common.eclass.
The first patch makes functions elisp-compile(), elisp-install(), etc.
die if there is an error. For EAPI 4, the functions died anyway,
because the underlying package manager functions did so.
In EAPIs where it is supported, nonfatal will give you the old
behaviour.
The second patch makes elisp-common.eclass cooperate with
readme.gentoo.eclass. Many of the ebuilds for elisp packages output
elog messages in postinst, so it makes sense to support this on the
eclass level.
Ulrich
next reply other threads:[~2013-03-08 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 19:56 Ulrich Mueller [this message]
2013-03-08 19:57 ` [gentoo-dev] [PATCH 1/2] elisp-common.eclass: Some functions now die on failure Ulrich Mueller
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.16989.965476.563290@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