From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tiff: build tiff2ps and tiff2pdf
Date: Fri, 03 May 2024 23:22:52 +0200 [thread overview]
Message-ID: <20240503212252.C7A9822238@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50111@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/50111#issuecomment-2093781445
Comment:
Here's one attempt. I'm not sure I have the `conflicts=` line right.
OTOH, I wonder if, even if `tiff2ps` and `tiff2pdf` are "unsupported" in tiff 4.6.0. Is it better to build them from tiff 4.4.0 (linked to old libtiff) or build them from tiff 4.6.0 (linked to new libtiff).
Moreover, it seems that `tiff5` is only kept to support a nonfree / binary only package `wps-office` so it might be dropped at some point.
So, here's an alternative proposal: use `--enable-tools-unsupported`, but move the unsupported tools (`tiff2ps` and `tiff2pdf`) to a separate package `tiff-unsupported`.
Note that upstream differentiates between "unsupported" tools (`tiff2ps` and `tiff2pdf`) which are "easy" to build via a configure switch, and "archived" tools (`fax2ps`, ...) which are not built with a configure switch if I'm not mistaken. See: https://gitlab.com/libtiff/libtiff/-/merge_requests/520.
I can implement the alternative proposal if you agree with it.
next prev parent reply other threads:[~2024-05-03 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 13:59 [PR PATCH] " tornaria
2024-05-03 2:02 ` cinerea0
2024-05-03 7:20 ` sgn
2024-05-03 7:21 ` sgn
2024-05-03 21:08 ` [PR PATCH] [Updated] " tornaria
2024-05-03 21:22 ` tornaria [this message]
2024-05-03 22:45 ` tornaria
2024-05-03 22:46 ` tornaria
2024-05-03 22:48 ` tornaria
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240503212252.C7A9822238@inbox.vuxu.org \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).