unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ali Bahrami <ali_gnu2@emvision.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefankangas@gmail.com>
Cc: schwab@linux-m68k.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Finding the dump (redux)
Date: Mon, 19 Apr 2021 09:41:17 -0600	[thread overview]
Message-ID: <1bf535b8-ca77-0eb6-9ac3-029b686b3671@emvision.com> (raw)
In-Reply-To: <83mttus5hs.fsf@gnu.org>

On 4/19/21 8:39 AM, Eli Zaretskii wrote:
>> From: Stefan Kangas <stefankangas@gmail.com>
>> Date: Mon, 19 Apr 2021 08:34:19 -0500
>> Cc: schwab@linux-m68k.org, rms@gnu.org, emacs-devel@gnu.org
>>
>> I would have hoped that we tried to ensure that builds are reproducible.
>> IOW, if the source hasn't changed, the fingerprint shouldn't change
>> either.
> 
> I don't see what do reproducible builds have to do with this.  Ali
> wasn't talking about rebuilding without changes.
> 

    That's true, but we do value reproducible builds. It's
hard to know up front sometimes, what information would be
good to share, and what would widen the discussion in
an unwanted way. It just hadn't come up yet.

When we update our systems, the packaging system only
updates the bits that have changed, so reproducible builds
mean that less data travels over the wire, and less data
has to be put in place on the updated system. The savings
are substantial, especially for a package like emacs, where
in principle, the bits only change when we update to
a new release, once every year or two. I'm not an expert,
but I think GNU/Linux installers are doing similar things,
for the same reasons. Distros don't want the bits to change
unless the source does.

It would also really help with that manifest problem.
Perhaps it is "paradise lost", but "paradise lost on
source change" would be a big upgrade.

- Ali



  reply	other threads:[~2021-04-19 15:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 19:38 Finding the dump (redux) Ali Bahrami
2021-04-17 18:45 ` Eli Zaretskii
2021-04-18  0:15   ` Ali Bahrami
2021-04-18  7:55     ` Eli Zaretskii
2021-04-18  8:18       ` Andreas Schwab
2021-04-18 16:05         ` Glenn Morris
2021-04-19  4:53         ` Richard Stallman
2021-04-19  8:35           ` Andreas Schwab
2021-04-19 13:00             ` Eli Zaretskii
2021-04-19 13:04             ` Ali Bahrami
2021-04-19 13:14               ` Eli Zaretskii
2021-04-19 13:34                 ` Stefan Kangas
2021-04-19 14:39                   ` Eli Zaretskii
2021-04-19 15:41                     ` Ali Bahrami [this message]
2021-04-19 15:58                       ` Eli Zaretskii
2021-04-19 16:08                         ` Ali Bahrami
2021-04-19 17:09                           ` Eli Zaretskii
2021-04-19  4:01       ` Ali Bahrami
2021-04-19 13:26         ` Stefan Monnier
2021-04-19 14:28           ` Eli Zaretskii
2021-04-19 14:50             ` Stefan Monnier
2021-04-19 15:43             ` Ali Bahrami
2021-04-19 16:06               ` Eli Zaretskii
2021-04-19 16:39                 ` Ali Bahrami
2021-04-19 17:19                   ` Eli Zaretskii
2021-04-19 18:03                     ` Ali Bahrami

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=1bf535b8-ca77-0eb6-9ac3-029b686b3671@emvision.com \
    --to=ali_gnu2@emvision.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=schwab@linux-m68k.org \
    --cc=stefankangas@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).