unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: chad <yandros@gmail.com>
Cc: theophilusx@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs 29.0.50 Snapshot binaries for WIndows
Date: Mon, 21 Feb 2022 21:38:59 +0200	[thread overview]
Message-ID: <831qzwui0c.fsf@gnu.org> (raw)
In-Reply-To: <CAO2hHWbxPWPEeKu5Jfq7xTyMEie3TmBz01csmhetOEh_WXL68Q@mail.gmail.com> (message from chad on Mon, 21 Feb 2022 13:41:16 -0500)

> From: chad <yandros@gmail.com>
> Date: Mon, 21 Feb 2022 13:41:16 -0500
> Cc: EMACS development team <emacs-devel@gnu.org>
> 
> This is a subtle but important point for anyone who is interested in semi-frequent snapshots (as opposed to
> releases). Under Windows, macOS, and a small subset of other systems (like Snap and Flatpak), these
> snapshots are typically contained to a single app-specific directory. Adding one is another directory; moving
> or removing one is likewise a single directory operation. On the other hand, the installed version of emacs on
> most GNU/Linux systems ends up with directories in several different directories, often in similar but not
> identical places from one distro to the next. This means that whatever tools are used to manage the
> snapshots need to track where things were added and, when multiple versions are installed simultaneously,
> which are to be removed (or shared, or overwritten). This sort of operation gets very quickly into the specifics
> of a distro, and thus is better handled within the mechanisms of that distro. Thankfully, this is already being
> done (and not just recently), for all of the major distros as far as I know, as well as for systems like Snap and
> (different but perhaps related) Docker.

There's no difference between Windows and Posix systems wrt to the
directories where Emacs components are installed.  the only difference
is that on Windows the top-level directory of the installation tree is
not a standard one, but one chosen by the user.  But under that
top-level directory, the tree is the same.  And if one installs
snapshots on a system with working environment, one is unlikely to
install each snapshot in its own top-level directory, because that
will require much more tinkering: change Path, amend INFOPATH, etc.

Bottom line: there shouldn't be a significant difference here between
installation on Posix systems and installation on Windows.  (macOS is
an entirely different ball game.)

And I don't think this aspect is very relevant to the issue at hand.



  reply	other threads:[~2022-02-21 19:38 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  3:37 Emacs 29.0.50 Snapshot binaries for WIndows Corwin Brust
2022-02-17  6:38 ` Eli Zaretskii
2022-02-17 12:41   ` H. Dieter Wilhelm
2022-02-18 18:18     ` Phillip Lord
2022-02-19  4:57 ` Richard Stallman
2022-02-19  5:09   ` Po Lu
2022-02-19  8:40   ` Eli Zaretskii
2022-02-20  4:31     ` Richard Stallman
2022-02-20  4:34       ` Po Lu
2022-02-21  4:35         ` Richard Stallman
2022-02-21  4:57           ` Po Lu
2022-02-23  6:46             ` Richard Stallman
2022-02-21  5:18           ` Eli Zaretskii
2022-02-21 12:06           ` Tim Cross
2022-02-21 18:41             ` chad
2022-02-21 19:38               ` Eli Zaretskii [this message]
2022-02-22  1:08                 ` Po Lu
2022-02-20  6:46       ` Eli Zaretskii
2022-02-21  4:35         ` Richard Stallman
2022-02-21 11:57         ` Dmitry Gutov
2022-02-24 22:41       ` phillip.lord
2022-02-19 11:14   ` Corwin Brust
2022-02-21  4:34     ` Richard Stallman
2022-02-23 14:33       ` Corwin Brust
2022-02-23 16:41         ` Stefan Monnier
2022-02-23 23:07           ` Corwin Brust
2022-02-24  6:55             ` Eli Zaretskii
2022-02-25  4:55               ` Corwin Brust
2022-02-25 11:28                 ` Phillip Lord
2022-02-25  5:00         ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2023-02-01  7:36 c.buhtz
2023-02-01 20:24 ` Corwin Brust
2023-02-19  9:56   ` c.buhtz
2023-02-19 18:05     ` Corwin Brust
2023-02-24  5:33       ` Troy Brown
2023-02-24  6:43         ` c.buhtz
2023-02-24  8:22           ` Eli Zaretskii
2023-02-24  8:47             ` c.buhtz
2023-02-24 11:40               ` Eli Zaretskii
2023-02-24 21:01                 ` c.buhtz
2023-02-24 21:17                   ` Eli Zaretskii
2023-02-24 21:42                     ` c.buhtz
2023-02-25  9:53                       ` Eli Zaretskii
2023-02-26 15:17                     ` c.buhtz
2023-02-26 15:48                       ` Eli Zaretskii
2023-03-10 18:49         ` Corwin Brust

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=831qzwui0c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=theophilusx@gmail.com \
    --cc=yandros@gmail.com \
    /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.savannah.gnu.org/cgit/emacs.git

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