From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH] Add gctp Date: Mon, 18 Jul 2016 17:47:23 -0400 Message-ID: <20160718214723.GA449@jasmine> References: <20160625172131.GC21038@jasmine> <20160627.210754.1991645543107797665.post@thomasdanckaert.be> <20160701203312.GA27184@jasmine> <20160707.094018.564247646166673024.post@thomasdanckaert.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55159) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPGO8-0005ON-C7 for guix-devel@gnu.org; Mon, 18 Jul 2016 17:47:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bPGO1-0003Cb-RZ for guix-devel@gnu.org; Mon, 18 Jul 2016 17:47:43 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:57081) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPGO0-0003Br-He for guix-devel@gnu.org; Mon, 18 Jul 2016 17:47:37 -0400 Content-Disposition: inline In-Reply-To: <20160707.094018.564247646166673024.post@thomasdanckaert.be> 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: Thomas Danckaert Cc: guix-devel@gnu.org On Thu, Jul 07, 2016 at 09:40:18AM +0200, Thomas Danckaert wrote: > 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? I'm not sure if there will be problems or not... it's unfortunately beyond my level of expertise :) I've asked someone with more experience than me to weigh in. > 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. Based on my experience with Guix so far, I think that maintaining our own forks of 3rd party software is outside of the scope of the Guix project. I think that the {nix,guix}-daemon is the only software for which we do this. If it's not possible to use the bundled GCTPs then we have to use an external library, but I think it should be maintained outside of Guix. As you say, it should not be much work to put it on a public Git repo or to host a tarball, since the development is basically complete. Too bad no other distros have already packaged it; often we can copy them ;) I'm sorry for the loooong delayed reply.