From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: build from source
Date: Fri, 2 Feb 2024 08:30:37 -0800 [thread overview]
Message-ID: <d51ed3e4-e5b5-461d-8748-afedf5b3050c@eastlink.ca> (raw)
In-Reply-To: <8924db85-5b87-4e91-b128-f16fd11b2a0b@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On 2024-02-01 22:00, Lawrence Velázquez wrote:
> It's not a great idea to make the unstable dev build your primary
> shell. If you just want to have it around for testing, you can run
> it directly out of the build directory when needed. (This is what
> I do.)
I have the same thing in mind -- I'll run the 'dev' just to see if I can
make myself useful possibly sniffing out a bug, but I want the stable
release to fall back to in case of trouble. I'm unclear as to the
situation with all the rest of whatever files might be associated with
the 'dev' tho. It's easy to just run the executable, but I'd worry
about some other change somewhere else in the project that might be a
dependency -- or is that not going to be an issue? And then there's,
say, Bart's, recent edit to 'zmv' -- will such things be included in a
'git' of the latest? 'make install' does the Linux thing and distributes
files here and there, which is standard, but ... well I dunno, maybe
there's nothing to worry about, but one might suppose that two complete
installations would be required -- one stable and one bleeding edge. Or
not. Maybe just the executable is the only thing that varies
'dangerously'. None of this is obvious.
[-- Attachment #2: Type: text/html, Size: 1981 bytes --]
prev parent reply other threads:[~2024-02-02 16:31 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
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 [this message]
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=d51ed3e4-e5b5-461d-8748-afedf5b3050c@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).