From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Corwin Brust Newsgroups: gmane.emacs.devel Subject: Re: windows Emacs-version issue Date: Fri, 6 May 2022 15:56:00 -0500 Message-ID: References: <857d70m4xd.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34606"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Sivaram Neelakantan , Emacs developers To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 06 22:56:56 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nn50R-0008mY-WB for ged-emacs-devel@m.gmane-mx.org; Fri, 06 May 2022 22:56:56 +0200 Original-Received: from localhost ([::1]:39904 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nn50Q-0000gy-QB for ged-emacs-devel@m.gmane-mx.org; Fri, 06 May 2022 16:56:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40476) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nn4zn-0007mr-5i for emacs-devel@gnu.org; Fri, 06 May 2022 16:56:15 -0400 Original-Received: from mail-ed1-f43.google.com ([209.85.208.43]:44976) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nn4zl-0006yG-Dn; Fri, 06 May 2022 16:56:14 -0400 Original-Received: by mail-ed1-f43.google.com with SMTP id t5so9975309edw.11; Fri, 06 May 2022 13:56:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DplVdQyl1OcGQ0OrR2+mIHmdiYZb4a/MKWK8BQ2CsEE=; b=omwKKA+fz2h6/ohYVrQ4qjSriRJuxAtY9oAkpQtPxXclGTU7oI0MmxVChYWGHHhEM3 kI4qMTPpwPyUXEeWCjFnnP2oZUW24KyBA7Nsq8NQcILmPF/Wx4CE87n01/3cnLajhvp3 GXLrcByey+M1lHZcmyH37mxa9WRyyfjyD9DzhE1nmJbsLbe4nn0pA5pYVPAHsyWELsMT 0Fns95FaTgpOo7d6oBdEzI10bmSRLCDqEitumDw/FsFbXhvjgHYT2zehaFw+/yeYJLEd N4ot+4uxtyVw4MXsf8EabGcfKkQZdJTjX+FNywwuoEajUXasKT2vQQiFs4Drav7aWpKk Sweg== X-Gm-Message-State: AOAM530bTYTvUmZYoIl8fBQ4p0jCgqiWdzULrIwTO9yCJ78FaGkrpPWB KTjyp6mFWm6aVlRXW3WQwKJonqUoLWZpig9xvBwqvgKW X-Google-Smtp-Source: ABdhPJxBR+2OAiTt1cmTBMaEVPO7S3qkrNOHjIoXwnHmZqZ5ev1yD3jDHKGqZ+Io8h75Joe6y20ZHZe+8+WjYEa4Jmk= X-Received: by 2002:a05:6402:d0a:b0:425:d455:452 with SMTP id eb10-20020a0564020d0a00b00425d4550452mr5488297edb.259.1651870571179; Fri, 06 May 2022 13:56:11 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=209.85.208.43; envelope-from=mplscorwin@gmail.com; helo=mail-ed1-f43.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:289343 Archived-At: Hi Glenn, Thanks for the reply. On Fri, May 6, 2022 at 3:48 PM Glenn Morris wrote: > > > I think the point being made here is that binary releases, like source > releases, should be version tagged, and once uploaded, should not be > replaced in-situ (because that eg breaks checksumming, and is generally > confusing). IMO the binaries uploaded to ftp.gnu.org/gnu/emacs/windows > should have some extra version string added to the filename, and it > should be incremented if a new build is uploaded. Eg "emacs-28.1-version1.zip". > > Ref https://lists.gnu.org/r/emacs-devel/2022-04/msg01108.html > for replacement of the original Windows files. The Windows binaries are created from the same source archive as is posted in the parent directory for the given Emacs version. When I've replaced the binary sett it has been to resolve issues with the build/packaging process. That said, I'm open to discussing new/additional conventions for naming that signify when the build occurred within the filenames if people generally thing that is helpful -- personally, I'd tend to find it confusing: I'd expect to find only one set of binaries for a given version (notwithstanding the new set that includes debug symbols, of course).. Perhaps others will weigh in.