From: "Tor-björn Claesson" <tclaesson@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 60640@debbugs.gnu.org
Subject: [bug#60640] Gnu: Add gdcm
Date: Sat, 14 Jan 2023 10:19:51 +0200 [thread overview]
Message-ID: <CAO0k703ksBh_5XYeVEEBbBKtgUejcUuZC=FZL2FwBNOJcPW59g@mail.gmail.com> (raw)
In-Reply-To: <87wn5q9epc.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
Hi,
Den lör 14 jan. 2023 kl 01:50 skrev Ludovic Courtès <ludo@gnu.org>:
>
> Could you send (in this issue) one patch that updates to 3.0, and
> another one to use system libraries?
>
I have a working update to 3.0.20. Except for other possible differences,
GDCM changes the name of the include directory between versions; I have to
e.g. #include <gdcm-2.8/gdcmImage.h> vs. <gdcm-3.0/gdcmImage.h>. How should
we deal with this? Would it make sense to leave a gdcm-2.8 package, to
cater for users of the older version, or should we expect people to follow
along?
Best regards!
Tor-björn
[-- Attachment #2: Type: text/html, Size: 943 bytes --]
next prev parent reply other threads:[~2023-01-14 8:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 19:40 [bug#60640] Gnu: Add gdcm Tor-björn Claesson
[not found] ` <handler.60640.B.167314095112989.ack@debbugs.gnu.org>
2023-01-08 7:59 ` [bug#60640] Acknowledgement (Gnu: Add gdcm) Tor-björn Claesson
2023-01-08 8:04 ` Tor-björn Claesson
2023-01-09 8:28 ` Tobias Geerinckx-Rice via Guix-patches via
2023-01-09 10:50 ` Tor-björn Claesson
2023-01-10 7:01 ` ( via Guix-patches via
2023-01-10 14:40 ` Tobias Geerinckx-Rice via Guix-patches via
2023-01-10 15:10 ` Tor-björn Claesson
2023-01-12 22:17 ` [bug#60640] Gnu: Add gdcm Ludovic Courtès
2023-01-13 10:45 ` Tor-björn Claesson
2023-01-13 23:50 ` Ludovic Courtès
2023-01-14 8:19 ` Tor-björn Claesson [this message]
2023-01-14 9:30 ` Tor-björn Claesson
2023-01-17 14:36 ` Ludovic Courtès
2023-01-14 17:06 ` Tor-björn Claesson
2023-01-17 14:38 ` Ludovic Courtès
2023-01-17 19:21 ` Tor-björn Claesson
2023-01-25 22:22 ` Ludovic Courtès
2023-01-20 11:30 ` Tor-björn Claesson
2023-01-20 12:44 ` Tor-björn Claesson
2023-01-25 22:01 ` Ludovic Courtès
2023-01-31 21:42 ` Tor-björn Claesson
2023-01-25 22:49 ` Ludovic Courtès
2023-01-27 15:06 ` Tor-björn Claesson
2023-01-14 19:34 ` Tor-björn Claesson
2023-01-14 21:58 ` Tor-björn Claesson
2023-01-10 14:52 ` Tobias Geerinckx-Rice via Guix-patches via
2023-01-11 5:29 ` Tor-björn Claesson
2023-01-12 11:21 ` Tor-björn Claesson
2024-02-19 22:41 ` bug#60640: " Sharlatan Hellseher
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='CAO0k703ksBh_5XYeVEEBbBKtgUejcUuZC=FZL2FwBNOJcPW59g@mail.gmail.com' \
--to=tclaesson@gmail.com \
--cc=60640@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).