From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: build from source
Date: Sat, 3 Feb 2024 15:42:00 -0800 [thread overview]
Message-ID: <0995fab4-58cd-4e13-856a-f85a884df62b@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7YAgAqENKu5CuqzbjpKX8HP++44mk7Njmi=Z13J-8Ga4g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On 2024-02-03 14:27, Bart Schaefer wrote:
> That would be from your OS distribution zsh package.
Right, I know these paths vary between distros, not zsh's problem.
> The default install path for packages NOT provided by the OS vendor is
> under /usr/local, yes.
Ok, so it's not an issue that distro info and user installed info are in
different places. No problem to solve.
>> ... shows 5.9 version. Funny thing is that 'dir' in '/usr/share/info'
>> has been updated so it would seem that it's anticipating an update to
>> the main info tree, but all the files are old. Is there a manual fix
>> for this?
> https://www.emacswiki.org/emacs/InfoPath
>
> The "info" program should recognize the equivalent.
>
Tx. Sounds like a nothing burger all round.
So the remaining questions are whether it's safe to run a dev build
within a stock 5.9 -- Lawrence seems to say so -- or whether to fret
about dependencies or no need. And what's the git command to grab the
latest and build it? I trust it will be simpler than installing from
scratch.
[-- Attachment #2: Type: text/html, Size: 2218 bytes --]
next prev parent reply other threads:[~2024-02-03 23:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 22:31 Ray Andrews
2024-02-01 23:15 ` Bart Schaefer
2024-02-02 1:36 ` Ray Andrews
2024-02-02 2:08 ` Bart Schaefer
2024-02-02 16:14 ` Ray Andrews
2024-02-02 17:08 ` Oliver Kiddle
2024-02-02 18:13 ` Ray Andrews
2024-02-02 23:06 ` Ray Andrews
2024-02-03 22:27 ` Bart Schaefer
2024-02-03 23:42 ` Ray Andrews [this message]
2024-02-04 1:26 ` Lawrence Velázquez
2024-02-04 2:00 ` Ray Andrews
2024-02-02 6:00 ` Lawrence Velázquez
2024-02-02 16:30 ` Ray Andrews
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=0995fab4-58cd-4e13-856a-f85a884df62b@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).