public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: [gentoo-commits] gentoo-x86 commit in net-analyzer/wireshark: wireshark-1.6.2.ebuild ChangeLog wireshark-1.4.9.ebuild wireshark-1.4.7.ebuild wireshark-1.6.0_rc1.ebuild wireshark-1.4.4.ebuild wireshark-1.4.6-r1.ebuild
Date: Tue, 13 Sep 2011 11:53:28 +0200	[thread overview]
Message-ID: <1315907608.4408.10.camel@raven.home.flameeyes.eu> (raw)
In-Reply-To: <20110913102855.0f572ac6@googlemail.com>

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

Il giorno mar, 13/09/2011 alle 10.28 +0100, Ciaran McCreesh ha scritto:
> In that case blocking just old versions is wrong, since if your
> installed version is broken and you try to reinstall, you'll need to
> uninstall first too.

It doesn't matter as much when it's the same version because then it
would have the same soversion and thus it wouldn't cause _visible_
trouble.

It might be interesting to note that it seems like rc4->final also
causes the same problem.

> (Incidentally, there's a bug in libtool that causes it to randomly link
> to stuff on / if you try to create an executable that links to both a
> built library and an installed library. It's probably fairly common,
> but people won't necessarily notice.)

Just for completeness sake, this can usually be fixed/worked around by
making sure to list just-built .la files _before_ the /usr libraries. I
had to work that around on opensc before. PAM also suffers from the same
issue _if_ the .la files are kept around.

-- 
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2011-09-13  9:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110912185552.543242004C@flycatcher.gentoo.org>
2011-09-13  8:42 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-analyzer/wireshark: wireshark-1.6.2.ebuild ChangeLog wireshark-1.4.9.ebuild wireshark-1.4.7.ebuild wireshark-1.6.0_rc1.ebuild wireshark-1.4.4.ebuild wireshark-1.4.6-r1.ebuild Markos Chandras
2011-09-13  9:23   ` Diego Elio Pettenò
2011-09-13  9:28     ` Ciaran McCreesh
2011-09-13  9:53       ` Diego Elio Pettenò [this message]
2011-09-13 10:24         ` [gentoo-dev] " Ciaran McCreesh
2011-09-13 13:58           ` Mike Frysinger
2011-09-14  5:17             ` Ciaran McCreesh
2011-09-13 13:59         ` Mike Frysinger
2011-10-11  5:31         ` Peter Volkov
2011-09-13  9:46   ` [gentoo-dev] " Tomáš Chvátal

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=1315907608.4408.10.camel@raven.home.flameeyes.eu \
    --to=flameeyes@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