From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Calling die in a subshell
Date: Sat, 15 Jun 2013 12:06:29 -0400 [thread overview]
Message-ID: <51BC9105.5070604@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The devmanual warns that calling die in a subshell does not work.
http://devmanual.gentoo.org/ebuild-writing/error-handling/index.html
This warning has been obsolete for some time; modern versions of
Portage handle die in a subshell just fine.
In fact, at least a couple of eclasses rely on this behavior. For
example, python-r1 uses subshells created by multiprocessing.eclass to
implement parallel "sub-phase" functions, any of which may call die on
failure.
Are there any objections to removing this warning from the devmanual?
Also, I believe there may be a question or two on the recruiting
quizzes that would need to be updated.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iF4EAREIAAYFAlG8kQUACgkQC77qH+pIQ6RMcAD/Ub0qkpXi/6tjNC/vHTXr2lLu
iprwtszsDnZGLOkmVKcA/R85pTIBT3Udo0Gc2/g2TJo6uzG8ppDbMc9bSHMgQtFf
=1qx7
-----END PGP SIGNATURE-----
next reply other threads:[~2013-06-15 16:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 16:06 Mike Gilbert [this message]
2013-06-15 16:14 ` [gentoo-dev] Calling die in a subshell Diego Elio Pettenò
2013-06-15 16:16 ` Ulrich Mueller
2013-06-15 16:19 ` hasufell
2013-06-15 16:21 ` Diego Elio Pettenò
2013-06-15 16:25 ` Ulrich Mueller
2013-06-15 17:41 ` Michał Górny
2013-06-16 13:00 ` Ulrich Mueller
2013-06-15 16:22 ` Mike Gilbert
2013-06-15 16:24 ` Tom Wijsman
2013-06-15 16:41 ` hasufell
2013-06-15 16:43 ` Ciaran McCreesh
2013-06-15 16:45 ` hasufell
2013-06-15 16:50 ` Ciaran McCreesh
2013-06-15 16:42 ` Ciaran McCreesh
2013-06-15 16:56 ` Mike Gilbert
2013-06-15 16:58 ` hasufell
2013-06-15 17:01 ` Ciaran McCreesh
2013-06-15 17:02 ` Mike Gilbert
2013-06-17 20:10 ` vivo75
2013-06-17 20:49 ` Mike Gilbert
2013-06-18 7:06 ` [gentoo-dev] " Duncan
2013-06-19 2:01 ` vivo75
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=51BC9105.5070604@gentoo.org \
--to=floppym@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