zsh-users
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@zsh.org>
To: zsh-users@zsh.org
Subject: Re: build from source
Date: Fri, 02 Feb 2024 01:00:00 -0500	[thread overview]
Message-ID: <8924db85-5b87-4e91-b128-f16fd11b2a0b@app.fastmail.com> (raw)
In-Reply-To: <b39d20a6-c5f4-4d83-bfdc-35fc1e10c968@eastlink.ca>

On Thu, Feb 1, 2024, at 8:36 PM, Ray Andrews wrote:
> Question, after getting the help done, next thing is 'make install', 
> now will that overwrite my existing 5.8?  I don't anticipate any issues 
> with 5.9 but if possible I'd like to keep 5.8 there in reserve, so 
> prevent any overwrites of, say, the stuff in /usr/share.../  or 
> wherever else.  I'm pretty sure I've done that previously -- kept the 
> new and the old side by side.  But not if it will be any trouble -- 5.9 
> isn't going to give me problems I don't think.  OTOH, If I'm running 
> the very latest build there's always that chance and I have to fire up 
> an older version due to some bug in the very latest.

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.)

-- 
vq


  parent reply	other threads:[~2024-02-02  6:01 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 [this message]
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=8924db85-5b87-4e91-b128-f16fd11b2a0b@app.fastmail.com \
    --to=larryv@zsh.org \
    --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).