From: kwshi <kwshi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] gifsicle vs. Gifsicle
Date: Tue, 04 May 2021 19:02:09 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30677@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
New issue by kwshi on void-packages repository
https://github.com/void-linux/void-packages/issues/30677
Description:
Currently the void-packages repo contains two _different_ packages named `gifsicle` (previously maintained by @pullmoll, now [orphaned](https://github.com/void-linux/void-packages/commit/f40cd776860a478ea987274897e9d64e7b44ea3e)) and `Gifsicle` (maintained by @ColdPhoenix00). That's a little bit confusing, and it's unclear, at first glance, why there are two separate packages for it and which one I should install.
Closer inspection w/ `xbps-query -Rf` and `xbps-query -R` reveals that `Gifsicle` provides an additional (GUI) executable named `gifview` and has an additional dependency on `libX11`. Both packages are otherwise the same (both provide `gifdiff` and `gifsicle`, along with their manpages).
I believe, for clarity's sake, these two packages should be reorganized/disambiguated somehow. I propose one of the following options:
1. Rename `Gifsicle` to `gifsicle-gui` to indicate its additional X dependency & the fact that it installs a GUI program (whereas plain `gifsicle` does not).
2. Rename `Gifsicle` to `gifsicle-gifview`, and remove the `gifdiff` and `gifsicle` binaries from that package, so that only `gifview` is provided by `gifsicle-gifview`. Maybe make `gifsicle-gifview` depend on `gifsicle`. This option avoids duplicating providers for `/usr/bin/gifdiff` and `/usr/bin/gifsicle`; this way, `gifsicle-gifview` is an _add-on_ rather than an alternative/conflict to plain `gifsicle`.
3. Remove either `Gifsicle` or `gifsicle`. The downside to this is that
- if we remove `Gifsicle`, then there will be no way to install `gifview`;
- if we remove `gifsicle`, then users will be forced to install `gifview` (together with its libX11 dependency) no matter what. Perhaps this option is acceptable, but it depends on what y'all think.
next reply other threads:[~2021-05-04 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 17:02 kwshi [this message]
2021-05-04 17:47 ` ericonr
2021-11-04 7:50 ` [ISSUE] [CLOSED] " Johnnynator
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30677@inbox.vuxu.org \
--to=kwshi@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).