Date: Thu, 21 Aug 2014 22:27:58 +0200 From: Tijl Coosemans <tijl@FreeBSD.org> To: Alexey Dokuchaev <danfe@nsu.ru> Cc: office@freebsd.org Subject: Re: devel/icu update nuisances Message-ID: <20140821222758.557cd456@kalimero.tijl.coosemans.org> In-Reply-To: <20140819015935.GA55266@regency.nsu.ru> References: <20140819015935.GA55266@regency.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Aug 2014 08:59:35 +0700 Alexey Dokuchaev wrote: > Hi there office@, > > I've just performed the dreaded update of devel/icu again, and of course > (as usual) it broke stuff all over the place. This is getting annoying. > > ICU manages to sneak into many executables, in a form (for example) of > libicu*.so.52, but under /usr/local/lib/compat/pkg me and ldconfig(8) can > one see these libicu*.so.52.1. Every time I have to manually make those > symlinks (.52 -> .52.1), otherwise many ports won't run until I rebuild > them. > > If this a known phenomena? Is portupgrade(1) not doing good job with > devel/icu (missing symlinks) or it's my local issue? Thanks, I suspect you have the COLLATION_FIX option enabled in devel/glib20. This makes everything that links to glib20 also link to icu. Because this option is off by default these ports don't get a revision bump when icu is updated. This propagation of icu will be fixed when glib20 switches to USES=libtool, which should happen together with the gnome3 import.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140821222758.557cd456>