From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Danckaert Subject: Re: [PATCH] Add gctp Date: Thu, 07 Jul 2016 09:40:18 +0200 (CEST) Message-ID: <20160707.094018.564247646166673024.post@thomasdanckaert.be> References: <20160625172131.GC21038@jasmine> <20160627.210754.1991645543107797665.post@thomasdanckaert.be> <20160701203312.GA27184@jasmine> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43738) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bL3vL-0006tK-Lq for guix-devel@gnu.org; Thu, 07 Jul 2016 03:40:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bL3vF-000704-Qc for guix-devel@gnu.org; Thu, 07 Jul 2016 03:40:38 -0400 Received: from s01-out.spamexperts.axc.nl ([159.253.0.252]:43904 helo=s01.spamexperts.axc.nl) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bL3vF-0006ze-K4 for guix-devel@gnu.org; Thu, 07 Jul 2016 03:40:33 -0400 In-Reply-To: <20160701203312.GA27184@jasmine> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: leo@famulari.name Cc: guix-devel@gnu.org From: Leo Famulari Subject: Re: [PATCH] Add gctp Date: Fri, 1 Jul 2016 16:33:12 -0400 > On Mon, Jun 27, 2016 at 09:07:54PM +0200, Thomas Danckaert wrote: >> Indeed, I believe GCTP is not maintained anymore, and each project using it >> makes a few small adjustments. From the changelog, it seems GCTP was last >> changed March 1998. > > In this case, I think it's appropriate to use the bundled GCTP. What do > others think? It's not a lot of work to submit a patch for HDF-EOS5 with the bundled GCTP, but I'm afraid that other packages which depend on two libraries that each bundle (a version of) GCTP (such as HDF-EOS2 and HDF-EOS5), will run into problems. There would be either a conflict due to multiple versions of libGctp, or, if we statically include GCTP in the libraries that use it, conflicting symbols when we link those libraries, no? For this reason, maybe using a separate GCTP package, and adding a patch to projects that use it, is the best solution after all? Development of GCTP and most packages that depend on it seems to be mostly finished anyway, so maintaining the patches might not be that much work. Thomas