Date: Wed, 24 Nov 2010 03:58:27 +0200 From: "Andrew W. Nosenko" <andrew.w.nosenko@gmail.com> To: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de> Cc: Koop Mast <kwm@rainbow-runner.nl>, freebsd-ports@freebsd.org Subject: Re: Renaming a shared library in the port-framework to match FreeBSD naming schemes? Message-ID: <AANLkTi=OqnAjvU_0rJW=w1BLmaUGjS%2BOKVAxnnOioDXd@mail.gmail.com> In-Reply-To: <4CEB1BE9.3070902@mail.zedat.fu-berlin.de> References: <4CE66051.7000600@zedat.fu-berlin.de> <20101119134636.2c5f44cc@headache.rainbow-runner.nl> <4CE683D1.1020300@zedat.fu-berlin.de> <AANLkTimHsAqRBndpqLvuL7GC-Hiu4o85dtTJfZky0%2BO-@mail.gmail.com> <4CE6B3D5.5040101@mail.zedat.fu-berlin.de> <AANLkTikJ3KMz-9ZqTuEOjc-_NzqxunVowSHZN6Vnv3G8@mail.gmail.com> <4CEAD07F.7060901@mail.zedat.fu-berlin.de> <AANLkTiks4YNn37x2u-sonKGwzQOmPQLf9C2xujF4kvsK@mail.gmail.com> <4CEB1BE9.3070902@mail.zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 23, 2010 at 03:42, O. Hartmann <ohartman@mail.zedat.fu-berlin.de> wrote: > On 11/23/10 02:14, Andrew W. Nosenko wrote: >> >> On Mon, Nov 22, 2010 at 22:20, O. Hartmann >> <ohartman@mail.zedat.fu-berlin.de> =A0wrote: >> >> But there lives another problem: Xerces people doesn't expect parallel >> installation of the "evelopment" part of Xerces-C (headers, >> pkg-config, etc). =A0At least it seems so by listing the libxerces-c >> package from Ubuntu. > > I guess so, but some ports of the FreeBSD ports (i.e. textproc/xalan-c) w= ant > xerces-c2 (which is 2.7.0). I try build xalan-c with the new xerces-c3 an= d > see if it can handle the new header and libraries. > >> >> I see three variants: >> (1) simple: just mark these ports (c2 and c3) as conflicting, > > ... in my testcase I did. And, for my personal taste, it is the best option. Be close to upstream as much as possible, IMHO, is the best way. >> (2) semi-simple: split each xerces-c port at the two: run-time and >> development. =A0Runtime contains a shered library, development contains >> anything other. =A0Mark development parts as conflictitng. > > ... well, in such a case we converge much to the weird Linux mess, I gues= s. > >> (3) move each port away from each other's way: move headers into own >> versioned deirectory (e.g. from include/xercesc/ to >> insclude/xercesc-3.1/xercesc/), drop libxerces-c.so (if any -- I don't >> know), rename pkg-config (.pc) file, and static library (if any), may >> be something yet another, like documentation -- need to look at the >> actual install. =A0All these changes hidden from the users through >> pkg-config's .pc, therefore only one problem for developers will be >> changed (non-standard name of the .pc file, i.e. pkg-config's module). > > ... this would bring up other complications for ports expecting libs and > headers at places where the solo installation normally resides. > >> =A0But ATM I see no better way to allow parallel installation of the >> packages that aren't intended for parallel installation by theirs >> authors... > > I tend to install it as a unique port with conflicts activated. Hope ther= e > are no further conflicts other than xalan-c. And I have some feelings that either existing xalan-c able to compile against current xerces-c or there is newer version that able. --=20 Andrew W. Nosenko <andrew.w.nosenko@gmail.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=OqnAjvU_0rJW=w1BLmaUGjS%2BOKVAxnnOioDXd>