From: g-branden-robinson <g-branden-robinson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: groff: update to 1.23.0.
Date: Tue, 01 Aug 2023 13:27:02 +0200 [thread overview]
Message-ID: <20230801112702.M-34cB7p9KYyfWGcj2A5gwSYjULon_IJe2nmK11idQE@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: 2614 bytes --]
New comment by g-branden-robinson on void-packages repository
https://github.com/void-linux/void-packages/pull/45300#issuecomment-1660120152
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")
Ah, thanks, I had forgotten about those since refactoring them away.
> 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.
Yes, `grog`, `groffer`, `gpinyin`, and `glilypond` (all written by the same contributor) had a similar structure, and on the _groff_ development mailing list we thought it would be simpler if these programs all became stand-alone scripts. So everything they need is now embedded in their executables in `$DESTDIR/bin`. Except for `groffer`, which we withdrew entirely.
You didn't find them in the `ChangeLog` because items in the `contrib` directory in _groff_'s source distribution (usually) maintain their own change log files as a consequence of their somewhat independent history. [Our LICENSES file](https://git.savannah.gnu.org/cgit/groff.git/tree/LICENSES?h=1.23.0#n31) suggests the basis for this, and [our HACKING file](https://git.savannah.gnu.org/cgit/groff.git/tree/HACKING?h=1.23.0#n46) covers it explicitly.
The Git history is probably easier to search because it records the changes to *everything* in one place.
```
commit 427a5cb1fc6761a0fd6e338d23732522b02804b0
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date: Sun Oct 9 07:00:05 2022 -0500
[glilypond]: Make script stand alone.
* contrib/glilypond/args.pl:
* contrib/glilypond/oop_fh.pl
* contrib/glilypond/subs.pl: Delete, moving their content into...
* contrib/glilypond/glilypond.pl: ...here. Also bump overall license to
GPLv3 from GPLv2 because all of the deleted files were GPLv3.
* contrib/glilypond/glilypond.am (dist_glilypond_DATA): Delete.
```
```
commit 92c5da8134a0209b7bf34e6f92bfa8218197d485
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date: Sun Oct 9 05:56:36 2022 -0500
[gpinyin]: Make script stand alone.
* contrib/gpinyin/subs.pl: Delete, moving its content into...
* contrib/gpinyin/gpinyin.pl: ...here.
(vowel_t): Use explicit list with `my`.
(vowel_n, vowel_t): Declare local scalar $vowel_with_tone using `my`.
* contrib/gpinyin/gpinyin.am (dist_gpinyin_DATA): Delete.
```
Does this help?
next prev parent reply other threads:[~2023-08-01 11:27 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
2023-08-01 11:24 ` g-branden-robinson
2023-08-01 11:25 ` g-branden-robinson
2023-08-01 11:27 ` g-branden-robinson [this message]
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=20230801112702.M-34cB7p9KYyfWGcj2A5gwSYjULon_IJe2nmK11idQE@z \
--to=g-branden-robinson@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).