unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: Richard Stallman <rms@gnu.org>
Cc: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>,
	Eli Zaretskii <eliz@gnu.org>,
	Phillip Lord <phillip.lord@russet.org.uk>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs 29.0.50 Snapshot binaries for WIndows
Date: Sat, 19 Feb 2022 05:14:09 -0600	[thread overview]
Message-ID: <CAJf-WoQEmAHUsw-bYaRV+wPsZ7QP0Gos5Nnx0Axmqrd2r1Y-_w@mail.gmail.com> (raw)
In-Reply-To: <E1nLHoG-0006rT-Gb@fencepost.gnu.org>

Thank you for commenting, Dr. Stallman.

On Fri, Feb 18, 2022 at 10:57 PM Richard Stallman <rms@gnu.org> wrote:
>
> [[[ 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. ]]]
>
>   > As much for my own testing as for yours, I have created a set of
>   > binary "snapshot" releases of Emacs for Windows.
>
> Do we have something lie this for GNU/Linux?

I would be happy to make similar point in time snapshots for
additional platforms.  Bob, of savannah hackers notoriety, has
suggested there are some servers that may be available to us that I
suspect would be suitable toward automating this process, e.g. Arch
would be easy to target, I think.

If this is a request I will look further, but see below.

> Or is there some reason why there is no need for them on GNU/Linux?

As others have said, distributions most provide all that is needed to
make either self-compilation from master trival, and to automate that
locally or via development repositories of packaged software.
Moreover, they accept into these repositories consistent (we hope, and
trust) with their own stated promises, with which we must trust
(actually: "teach") users to have understood and, indeed, to prefer.
(They did select this distro/OS, after all..)

So, if we try to make snapshots for GNU/Linux, we are likely "chasing
the tail" of efforts happening (and which, indeed, should be
happening) nearer to users' explicitly trusted sources/controls (for
example, when taking in pre-built versions of Emacs' dependencies for
their platform, when not building those from sources).

Perhaps another approach could do something similar that might be more
interesting to GNU/Linux users..

Firstly ,I consider the impact in this case to be "bug reports".  In
creating snapshot and pre-release builds, our goal is to help find
platform specific problems as soon as possible before making
(especially xx.1) releases. Also, when we invite those users who
can't/won't compile Emacs from the git repository for themselves, we
are creating additional opportunities for people to become involved
with Emacs development, and perhaps the GNU project and the Free
Software Foundation.

[[As others have said "up thread", and I hope is clear, it is really
fairly easy to self-build Emacs, at this point, on nearly any "flavor"
of GNU/Linux user environment, almostly certainly more so than
"anywhere else". ]]

My first idea is to use the infrastructure had Bob mentioned may be
available to create automated snapshots builds once or several times
per day, each using a different GNU/Linux distribution.  We could then
run Emacs' test suite, They results of these runs would be sent via
email to "a few people" -- actually, via a new
"emacs-continuous-build@gnu.org list, but I think few would subscribe
;)  Running some automated form(s) of the performance metrics SM and
Andreas have been discussing seems like a very tempting target, if
something like this is attempted.

A second, and likely compatible/interconnected idea to document
"recipies" for self-building Emacs, perhaps putting such a document
into admin/README.SNAPSHOT-DISTRO.  For such providers as Debian, this
is likely a matter of finding the right file to quote.   In fact (to
me) this seems like a terrible task, to keep such a document current.
In fact, the only way I can think to manage the task that sounds like
fun would be to automatically pull the recipes used for a "continuous
build testing" implementation.  But, since all the software involved
here would be Free Software, there is no reason that cannot be done.

Sorry for sending such a long message to answer such short questions.
I happen to think there's an important opportunity in creating builds
of Emacs and testing them automatically.  I hope you find the idea(s)
interesting.

>
> It would not be right to give more support to Windows than to
> the GNU system itself.
>
> --
> Dr Richard Stallman (https://stallman.org)
> Chief GNUisance of the GNU Project (https://gnu.org)
> Founder, Free Software Foundation (https://fsf.org)
> Internet Hall-of-Famer (https://internethalloffame.org)
>
>



  parent reply	other threads:[~2022-02-19 11:14 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
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 [this message]
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=CAJf-WoQEmAHUsw-bYaRV+wPsZ7QP0Gos5Nnx0Axmqrd2r1Y-_w@mail.gmail.com \
    --to=corwin@bru.st \
    --cc=dieter@duenenhof-wilhelm.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    --cc=rms@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).