From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pdftk: update to 3.3.3.
Date: Wed, 15 Nov 2023 18:25:30 +0100 [thread overview]
Message-ID: <20231115172530.Fa8P27f_e4PL0V42dKJ4GG8x3urJVkDj48LfKBU5Obk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47189@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/47189#issuecomment-1812958051
Comment:
> I don't think that just replacing the content of the package is the right approach to this since it appears to me that they are two different pieces of software from different authors (although with virtually the same functionality). Imho it would be better to just remove the pdftk package and offer a new one under a different name (pdftk-java seems to be a common choice
If `pdftk` is removed and replaced by `pdftk-java`, isn't that basically the same thing as just replacing the package contents, in effect? (difference being `pdftk` becoming a transitional dummy package, I guess)
next prev parent reply other threads:[~2023-11-15 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 0:30 [PR PATCH] " classabbyamp
2023-11-13 0:39 ` [PR PATCH] [Updated] " classabbyamp
2023-11-13 1:10 ` classabbyamp
2023-11-13 1:19 ` classabbyamp
2023-11-15 17:06 ` Hoshpak
2023-11-15 17:25 ` classabbyamp [this message]
2023-11-15 17:26 ` classabbyamp
2023-11-15 17:36 ` [PR PATCH] [Updated] " classabbyamp
2023-11-15 19:11 ` [PR PATCH] [Merged]: pdftk: replace with pdftk-java classabbyamp
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=20231115172530.Fa8P27f_e4PL0V42dKJ4GG8x3urJVkDj48LfKBU5Obk@z \
--to=classabbyamp@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).