Github messages for voidlinux
 help / color / mirror / Atom feed
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 05:00:53 +0200	[thread overview]
Message-ID: <20230801030053.yw-FGeqG_QY8L5HarpYjrYJPd7hXa1KxyW-FWxoAK4s@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: 1012 bytes --]

New comment by g-branden-robinson on void-packages repository

https://github.com/void-linux/void-packages/pull/45300#issuecomment-1659491401

Comment:
Hi there,

Interested novelist here.

>     * `--with-doc` configure option removed upstream, builds/installs docs by default

Half-true.  Docs are built by the default `make` target, but `install-doc` is still required to install them.  This is an Automake convention that I am not thrilled with.

>     * `${DESTDIR}/usr/lib` is empty, so no more `libgroff` - although can't find it mentioned in the changelog (which is [a whole novel](https://git.savannah.gnu.org/cgit/groff.git/tree/ChangeLog.123))

It wasn't ever supposed to be there.  `libgroff`, like a handful of others in the _groff_ source tree, is internal.  It has no published or supported API, it is not documented at all, it is built as a static object, and it is statically linked with the executables that need it.  If anyone was ever shipping `libgroff.a`, they were in error.



  parent reply	other threads:[~2023-08-01  3:00 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 [this message]
2023-08-01 10:36 ` 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
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=20230801030053.yw-FGeqG_QY8L5HarpYjrYJPd7hXa1KxyW-FWxoAK4s@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).