unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Question on updating to 29.1
Date: Sat, 12 Aug 2023 09:23:20 +0300	[thread overview]
Message-ID: <83leegg4o7.fsf@gnu.org> (raw)
In-Reply-To: <8b321ed5-89a9-fa19-d819-2b31cce464aa@magnaspesmeretrix.org> (message from PierGianLuca on Sat, 12 Aug 2023 08:08:59 +0200)

> Date: Sat, 12 Aug 2023 08:08:59 +0200
> From: PierGianLuca <luca@magnaspesmeretrix.org>
> 
> Hi Eli,
> 
> > The Emacs installation method is designed in a way that allows you to
> > have several Emacs versions installed on the same system.  Only one of
> > them, the one you installed the last, is invoked by the name "emacs",
> > but all the others can be invoked by their numbered names, as in
> > "emacs-28.2" etc.  An installed version of Emacs will only be removed
> > if you explicitly run "make uninstall" in the build directory of that
> > version.
> 
> 
> Thank you, this is very useful information. Wouldn't this be useful in the INSTALL files? or maybe it's already there. I might want to keep one previous version just in case, but no other.

This is standard GNU structure of Make targets, every GNU project
follows that.  You can find the list of standard targets in the node
"Standard Targets" of the "GNU Coding Standards" document.

I find no reason to duplicate that information in Emacs, as that would
waste space for no good reason, and will not be discoverable enough to
make the difference anyway.  Stuff that "just works" doesn't need any
prominent documentation in the first place.

> Should I do "make uninstall" for the previous version after I install the new version, or before, or it doesn't matter?

It's up to you.  I personally never uninstall old Emacs versions, but
that's because having them makes it easy for me, as an Emacs
developer, to check how old versions behaved in specific situations
and when did a specific bug start to happen.  Another consideration is
that if you upgrade your system, some old versions might not run
anymore, at which time they are just using up disk space, and should
probably be removed.  (In this regard my hat off to Microsoft, because
I still have a Windows port of Emacs 21.4, built 17 years ago, running
just fine on my current MS-Windows system, after several OS
migrations, whereas Trisquel GNU/Linux, for example, tends to break
binaries compiled with older OS versions upon every significant OS
upgrade.)



  reply	other threads:[~2023-08-12  6:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  8:11 Question on updating to 29.1 PierGianLuca
2023-08-11  8:21 ` Philip Kaludercic
2023-08-11  8:45   ` PierGianLuca
2023-08-11  8:54     ` Basile Starynkevitch
2023-08-11 10:16       ` Emanuel Berg
2023-08-11 11:20         ` Basile Starynkevitch
2023-08-11 12:20           ` Emanuel Berg
2023-08-17 16:17         ` PierGianLuca
2023-08-17 17:01           ` Corwin Brust
2023-08-17 17:55             ` PierGianLuca
2023-08-17 18:58           ` Basile Starynkevitch
2023-10-05 18:21             ` hw
2023-10-05 18:54               ` Eli Zaretskii
2023-08-18 19:24           ` Philip Kaludercic
2023-08-19 11:05             ` Pop-up font size with lucid toolkit (was: Question on updating to 29.1) PierGianLuca
2023-08-19 11:10               ` Solved: " PierGianLuca
2023-08-19 11:13               ` Gregory Heytings
2023-08-19 11:15                 ` PierGianLuca
2023-08-20 12:36               ` Pop-up font size with lucid toolkit Philip Kaludercic
2023-08-20 13:13                 ` PierGianLuca
2023-08-21 15:14                   ` Philip Kaludercic
2023-08-11 11:16     ` Question on updating to 29.1 Eli Zaretskii
2023-08-11 22:04       ` Jens Schmidt via Users list for the GNU Emacs text editor
2023-08-12  5:48         ` Eli Zaretskii
2023-08-12  6:08           ` PierGianLuca
2023-08-12  6:23             ` Eli Zaretskii [this message]
2023-08-13 12:46           ` Petteri Hintsanen
2023-10-05 11:44 ` Byung-Hee HWANG
2023-10-05 17:17   ` Emanuel Berg
2023-10-06 23:51     ` Byung-Hee HWANG
2023-10-07  7:43       ` Yuri Khan
2023-10-07 12:13         ` Byung-Hee HWANG
2023-10-07 12:28           ` Question on updating to 29.1 (on Ubuntu) PierGianLuca
2023-10-23 16:41       ` Question on updating to 29.1 Basile Starynkevitch
2023-10-06  1:30   ` Emanuel Berg
2023-10-07  6:06     ` జిందం వాఐి

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83leegg4o7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).