From owner-freebsd-ports@FreeBSD.ORG Wed Nov 24 01:58:30 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3796106566B for ; Wed, 24 Nov 2010 01:58:29 +0000 (UTC) (envelope-from andrew.w.nosenko@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id A37288FC16 for ; Wed, 24 Nov 2010 01:58:29 +0000 (UTC) Received: by qwi4 with SMTP id 4so277108qwi.13 for ; Tue, 23 Nov 2010 17:58:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=d1HvjB7C8UI/nS4gSDDxVaj1khF1U7kMwL4mBy1zDkg=; b=tDiiLgzJOKmChlUMI2pe/1I2fo7qvLiBS/9UMJn2fMcuw/3tLLRNeTmVJyGjb2DU2v PIU8bR0WDyOfdX3tGH30NHZAVyU5r/LsqVGet5uqA2V3X/84urdPABNFJc34UvSXAgCv Fm/ttBGyn044I5/b+Rfh9q9bo1bKDwn0K/C8o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=CKHw3PGM/VIa8XoyErsUZ+sdxWep7LvB7V/QSUL6sutqcjTF5xFt6zcIPEVAJzwsyc F2I5MCMZnOCp17AWS3lt74wUvCUYrk8cV6JMaqd/wUjcy9FA+kYtwN1qN77F++uF56gV 3zbYGd/pp6BzRwgNXzxAi8irRNzu8ACkJgBRA= MIME-Version: 1.0 Received: by 10.229.251.204 with SMTP id mt12mr6888821qcb.182.1290563907995; Tue, 23 Nov 2010 17:58:27 -0800 (PST) Received: by 10.229.95.209 with HTTP; Tue, 23 Nov 2010 17:58:27 -0800 (PST) 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> <4CE6B3D5.5040101@mail.zedat.fu-berlin.de> <4CEAD07F.7060901@mail.zedat.fu-berlin.de> <4CEB1BE9.3070902@mail.zedat.fu-berlin.de> Date: Wed, 24 Nov 2010 03:58:27 +0200 Message-ID: From: "Andrew W. Nosenko" To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Koop Mast , freebsd-ports@freebsd.org Subject: Re: Renaming a shared library in the port-framework to match FreeBSD naming schemes? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2010 01:58:30 -0000 On Tue, Nov 23, 2010 at 03:42, O. Hartmann wrote: > On 11/23/10 02:14, Andrew W. Nosenko wrote: >> >> On Mon, Nov 22, 2010 at 22:20, O. Hartmann >> =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