From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AB5F71396D0 for ; Tue, 29 Aug 2017 20:38:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6141BE0E92; Tue, 29 Aug 2017 20:38:23 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 18770E0E85 for ; Tue, 29 Aug 2017 20:38:22 +0000 (UTC) Received: from [192.168.1.100] (c-98-218-46-55.hsd1.md.comcast.net [98.218.46.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id E050D33BF43 for ; Tue, 29 Aug 2017 20:38:21 +0000 (UTC) To: gentoo-dev@lists.gentoo.org From: Michael Orlitzky Subject: [gentoo-dev] Of death and prerm Message-ID: <09043e39-bcec-f73b-683e-17de59b8e5d5@gentoo.org> Date: Tue, 29 Aug 2017 16:38:15 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Archives-Salt: 0e74dafc-c5da-4b69-bd93-47dbd95a8dca X-Archives-Hash: 9c764b39e47b79290bcbf967fe5f0b38 What should happen if an ebuild calls "die" in pkg_prerm? The issue arose while trying to create a package that could not be uninstalled except as part of an upgrade. The first thing that came to mind was to have it die in pkg_prerm. What portage does is *appear* to crash, but then continue along as if nothing happened. Does the PMS cover this indirectly? (Is there a reliable way to make package removal fail?)