From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: perl_base not in Base ?
Date: Thu, 30 Dec 2021 08:34:52 -0500 [thread overview]
Message-ID: <1eaeb163-bb66-f3b4-ddf8-aae9a85e913c@cornell.edu> (raw)
In-Reply-To: <e8082aa7-d4b0-5f3f-115d-a84607311f0f@Nexgo.DE>
On 12/30/2021 5:38 AM, Achim Gratz wrote:
> Am 29.12.2021 um 17:12 schrieb Jon Turney:
>> I think this was the case, at one time.
>
> As I said before, at least info still does; not directly, though (it requires a
> bunch of Perl module distribution that will then pull in perl_base at least).
No, info just requires a few libs. You're thinking of texinfo, but it's not in
Base.
Ken
next prev parent reply other threads:[~2021-12-30 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 10:57 Marco Atzeri
2021-12-29 8:51 ` Achim Gratz
2021-12-29 14:25 ` Ken Brown
2021-12-29 14:36 ` Marco Atzeri
2021-12-29 16:12 ` Jon Turney
2021-12-30 10:38 ` Achim Gratz
2021-12-30 13:34 ` Ken Brown [this message]
2021-12-30 10:36 ` Achim Gratz
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=1eaeb163-bb66-f3b4-ddf8-aae9a85e913c@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).