From: Philip Kaludercic <philipk@posteo.net>
To: PierGianLuca <luca@magnaspesmeretrix.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Question on updating to 29.1
Date: Fri, 11 Aug 2023 08:21:37 +0000 [thread overview]
Message-ID: <87350qj8fi.fsf@posteo.net> (raw)
In-Reply-To: <7434968f-40b1-ac55-c692-56a9b1c6a547@magnaspesmeretrix.org> (PierGianLuca's message of "Fri, 11 Aug 2023 10:11:46 +0200")
PierGianLuca <luca@magnaspesmeretrix.org> writes:
> Hi everyone!
>
> I have version 28.1 that I "make install"ed on a Ubuntu machine, for
> the first time. I'd like to update to 29.1 and my question is: do I
> need to do anything about the old version? it will simply be replaced?
> I can't find anything about this in the official documentation, say at
Did you install version 28.1 from a Git checkout or from a tarball? If
you have used Git to fetch the source, you should be able to update to
the most recent version of Emacs using a "git pull" or "git checkout
emacs-29" (or whatever other branch, tag, commit). If you have
installed it from a tarball, you will need to download a new release.
This link should redirect you to a close-by FTP mirror:
http://ftpmirror.gnu.org/emacs/emacs/emacs-29.1.tar.xz
The installation procedure should be similar or even analogous to the
installation for Emacs 28, with the possible exception of additional
./configure flags that you might be interested in, which have been added
in Emacs 29.
> https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL
>
> Sorry if the question is silly or my terminology is not correct – I'm quite unfamiliar with compilation and versioning.
>
> Cheers,
> Luca
next prev parent reply other threads:[~2023-08-11 8:21 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 [this message]
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
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=87350qj8fi.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=help-gnu-emacs@gnu.org \
--cc=luca@magnaspesmeretrix.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).