From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add gctp
Date: Mon, 18 Jul 2016 15:02:47 +0200 [thread overview]
Message-ID: <87r3arnloo.fsf@gnu.org> (raw)
In-Reply-To: <20160707.094018.564247646166673024.post@thomasdanckaert.be> (Thomas Danckaert's message of "Thu, 07 Jul 2016 09:40:18 +0200 (CEST)")
Thomas Danckaert <post@thomasdanckaert.be> skribis:
> From: Leo Famulari <leo@famulari.name> 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.
Leo, what’s your take on this? It seems we’ve forgotten about this
patch for too long already. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-07-18 13:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 12:40 [PATCH] Add gctp Thomas Danckaert
2016-06-18 1:39 ` Leo Famulari
2016-06-18 9:05 ` Thomas Danckaert
2016-06-21 6:35 ` Thomas Danckaert
2016-06-25 17:21 ` Leo Famulari
2016-06-27 19:07 ` Thomas Danckaert
2016-07-01 20:33 ` Leo Famulari
2016-07-07 7:40 ` Thomas Danckaert
2016-07-18 13:02 ` Ludovic Courtès [this message]
2016-07-18 21:47 ` Leo Famulari
2016-09-15 17:08 ` Thomas Danckaert
2016-09-24 1:08 ` Leo Famulari
2016-09-24 19:49 ` Thomas Danckaert
2016-09-27 17:38 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2016-06-17 12:41 Thomas Danckaert
2016-06-17 9:29 Thomas Danckaert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3arnloo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=post@thomasdanckaert.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).