From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [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, 11 Oct 2011 09:31:18 +0400 [thread overview]
Message-ID: <1318311078.21990.28.camel@tablet> (raw)
In-Reply-To: <1315907608.4408.10.camel@raven.home.flameeyes.eu>
В Втр, 13/09/2011 в 11:53 +0200, Diego Elio Pettenò пишет:
> 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.
wireshark relinks against system wsutil library during 'make DESTDIR=
${D} install', so once wireshark-1.6 is installed we have
libwsutil.so.1.0.0. There is nothing bad linking with correct library
version (even though binary came from previous version).
> 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.
Well, I can just drop _rc part in blocker. _rc versions were hardmasked
anyway.
> 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.
Hm interesting. Actually I've tried to strace libtool and it have not
touched system .la files but since we drop .la anyway I'll recheck.
--
Peter.
next prev parent reply other threads:[~2011-10-11 5:33 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 ` [gentoo-dev] " Diego Elio Pettenò
2011-09-13 10:24 ` 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 [this message]
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=1318311078.21990.28.camel@tablet \
--to=pva@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