unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs 29.0.50 Snapshot binaries for WIndows
Date: Mon, 21 Feb 2022 23:06:13 +1100	[thread overview]
Message-ID: <87wnhommwq.fsf@gmail.com> (raw)
In-Reply-To: <E1nM0Pt-0008Sb-FC@fencepost.gnu.org>


Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > > The "snapshot" releases are apparently something else.  How are they
>   > > different from the Windows binaries volunteers have made in the past?
>
>   > They aren't made from releases but from copies ("snapshots") of the
>   > development tree.
>
> Thanks.  Now I know concretely what the issue is, and I can draw some
> conclusions.
>
> The issue is a matter of the priorities of our project.  We should not
> be catering to Windows (or MacOS, or any nonfree system) more than we
> cater to the GNU system, because GNU and the Free World get priority
> on principle.
>
> If people using versions the GNU system have no need for snapshots
> like these (perhaps because they are all happier compiling the sources
> themselves, as some have suggested), then then these snapshots don't
> raise a moral issue.
>
> But if in fact users of some GNU/Linux distros would like this kind of
> snapshot too, we should provide this sort of help on those distros
> before we provide it on Windows.
>
> It's not a matter of _who_ does the work, it's a matter of which work
> gets done.

It might be worth noting that manyh of the GNU Linux distributions have
community generated binary package 'snapshots'. For example Debian and
Ubuntu do. However, I think many people on GNU Linux systems are happy
enough with just building from the git repository (I get the impression
this is something which is much easier to do than on platforms like
WIndows where there is probably a higher number of people who don't have
the requisite build tools installed). In some ways, it probably makes
sense to leave snapshots for GNU Linux distros to the communities
associated with each distro as those community efforts will also work to
ensure the snapshot complies with distrobution specific package formats
and installation standards. For example, Debian and Ubuntu have
additional Emacs site code to support those distros ability to have
multiple versions of Emacs installed at the same time. It also means
users can install the snapshots using the package management system they
are familiar with and there is less chance of causing issues when their
distro updates to newer versions.



  parent reply	other threads:[~2022-02-21 12:06 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 [this message]
2022-02-21 18:41             ` chad
2022-02-21 19:38               ` Eli Zaretskii
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=87wnhommwq.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-devel@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.
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).