public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Of death and prerm
Date: Wed, 30 Aug 2017 10:04:55 +0200	[thread overview]
Message-ID: <20170830100455.1c4fbccf@gentoo.org> (raw)
In-Reply-To: <09043e39-bcec-f73b-683e-17de59b8e5d5@gentoo.org>

On Tue, 29 Aug 2017 16:38:15 -0400
Michael Orlitzky <mjo@gentoo.org> wrote:

> 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?)

Is there any point in dying in any phase after (or during)
pkg_postinst ?
files are already live by then; what would this achieve ?


  reply	other threads:[~2017-08-30  8:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 20:38 [gentoo-dev] Of death and prerm Michael Orlitzky
2017-08-30  8:04 ` Alexis Ballier [this message]
2017-08-30 13:04   ` Michael Orlitzky
2017-08-30  9:25 ` Michał Górny
2017-08-30 13:15   ` Michael Orlitzky
2017-08-30 13:26     ` Ulrich Mueller
2017-08-30 13:32       ` Michael Orlitzky
2017-08-30 13:40         ` Ulrich Mueller
2017-08-30 13:46           ` Ian Stakenvicius
2017-08-30 14:04             ` Michael Orlitzky
2017-08-30 14:10               ` Ian Stakenvicius
2017-08-30 14:24                 ` Michael Orlitzky
2017-08-30 15:04                   ` Michael Orlitzky
2017-08-30 14:29             ` Ulrich Mueller
2017-08-30 14:45     ` Michał Górny

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=20170830100455.1c4fbccf@gentoo.org \
    --to=aballier@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