public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Unnecessary logs: has_version to the rescue?
Date: Wed, 31 Mar 2010 21:19:04 +0100	[thread overview]
Message-ID: <20100331211904.0f49cae0@snowmobile> (raw)
In-Reply-To: <4BB3ABC8.7050207@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

On Wed, 31 Mar 2010 22:08:40 +0200
Sebastian Pipping <sping@gentoo.org> wrote:
> Is there some kind of evilness in this usage of has_version that I am
> not aware of?

Unfortunately, yes.

Historically, has_version in pkg_postinst would return results based
upon the version that *was* installed. This feature was widely used to
display context-aware post-install messages, and there were examples of
it in the documentation. Portage then silently changed this behaviour,
without an EAPI bump and without changing the documentation, breaking
all those packages in the process. The resulting mess discouraged many
people from bothering with that kind of thing...

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-03-31 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 20:08 [gentoo-dev] Unnecessary logs: has_version to the rescue? Sebastian Pipping
2010-03-31 20:19 ` Ciaran McCreesh [this message]
2010-03-31 20:29   ` Sebastian Pipping
2010-03-31 20:32     ` Ciaran McCreesh
2010-03-31 20:31   ` Zac Medico
2010-03-31 20:37     ` Sebastian Pipping
2010-03-31 20:42       ` Zac Medico
2010-03-31 20:52         ` Sebastian Pipping
2010-03-31 21:05           ` Zac Medico
2010-03-31 21:16             ` Sebastian Pipping
2010-03-31 21:32               ` Zac Medico

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=20100331211904.0f49cae0@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --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