From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: groff: update to 1.23.0.
Date: Tue, 01 Aug 2023 12:54:05 +0200 [thread overview]
Message-ID: <20230801105405.LqCd_Y-sdX0crI6jaaYzr7HnxpKhRdbG4Qk3JXtqVkk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45300@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
New comment by icp1994 on void-packages repository
https://github.com/void-linux/void-packages/pull/45300#issuecomment-1660071990
Comment:
Thank you for your inputs. The `libgroff` package in Void wasn't actually shipping `libgroff.a`, rather the following files (i.e., everything installed under "$destdir/usr/lib")
```
/usr/lib/groff/glilypond/args.pl
/usr/lib/groff/glilypond/oop_fh.pl
/usr/lib/groff/glilypond/subs.pl
/usr/lib/groff/gpinyin/subs.pl
/usr/lib/groff/groff_opts_no_arg.txt
/usr/lib/groff/groff_opts_with_arg.txt
/usr/lib/groff/groffer/main_subs.pl
/usr/lib/groff/groffer/man.pl
/usr/lib/groff/groffer/split_env.sh
/usr/lib/groff/groffer/subs.pl
/usr/lib/groff/groffer/version.sh
/usr/lib/groff/grog/subs.pl
```
The changelog mentions that groffer/*, groff_opts_{no,with}_arg.txt, and grog/subs.pl were all removed. Although not sure about the other ones.
next prev parent reply other threads:[~2023-08-01 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 17:20 [PR PATCH] " icp1994
2023-07-28 18:52 ` [PR PATCH] [Updated] " icp1994
2023-07-28 18:58 ` icp1994
2023-07-28 19:25 ` icp1994
2023-07-28 19:32 ` icp1994
2023-08-01 3:00 ` g-branden-robinson
2023-08-01 10:36 ` [PR PATCH] [Updated] " icp1994
2023-08-01 10:54 ` icp1994 [this message]
2023-08-01 11:24 ` g-branden-robinson
2023-08-01 11:25 ` g-branden-robinson
2023-08-01 11:27 ` g-branden-robinson
2023-08-01 14:00 ` [PR PATCH] [Updated] " icp1994
2023-08-01 14:00 ` icp1994
2023-08-05 18:50 ` [PR PATCH] [Merged]: " leahneukirchen
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=20230801105405.LqCd_Y-sdX0crI6jaaYzr7HnxpKhRdbG4Qk3JXtqVkk@z \
--to=icp1994@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).