all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christoph Scholtes <cschol2112@googlemail.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: emacs-devel@gnu.org
Subject: Re: Precompiled Emacs binaries, where are the sources?
Date: Sun, 11 Dec 2011 14:10:44 -0700	[thread overview]
Message-ID: <4EE51C54.2080503@gmail.com> (raw)
In-Reply-To: <20197.3215.481133.654911@a1i15.kph.uni-mainz.de>

On 12/11/2011 1:03 PM, Ulrich Mueller wrote:

> Where can I find the sources for the precompiled Emacs binaries in
> <ftp://alpha.gnu.org/gnu/emacs/pretest/windows/>, e.g. for the 24.0.91
> pretest? The README file points to the parent directory ...
>
> | * IMPORTANT LEGAL REMINDER
> |
> |   If you want to redistribute any of the precompiled distributions
> |   of Emacs, be careful to check the implications of the GPL.  For
> |   instance, if you put the emacs-23.1.91-bin-i386.tar.gz file from
> |   this directory on an Internet site, you must arrange to distribute
> |   the source files of the SAME version (i.e. ../emacs-23.1.91.tar.gz).
>
> ... but looks like all sources have been deleted from there, except for
> the newest one (24.0.92).

The README that the ftp server shows should probably be version 
independent and more generic, but nevertheless this looks like an issue.

Then, if what Ulrich reported is really an issue, and according to the 
Legal Reminder it probably is, what about the weekly Windows snapshots 
we have been providing? They are created directly off of the bzr source 
tree and don't have an associated source tarball. Now, it would not be 
too hard to also create a source tarball for these snapshots and provide 
it with the binary distributions. For all distributions I created that 
have the bzr revno specified it is also possible to recreate the 
appropriate source tarball and upload it.

I would propose this: remove all binary builds except the last 5 and 
provide source tarballs for those. In the future only keep 5 versions of 
the binary distros on the server. This should be enough for people to be 
able to rollback in case there is issues with the weekly builds.

We should also create a README file for the weekly build section and 
show it like the pretest section of the ftp server does.

WDYT?

Christoph



  reply	other threads:[~2011-12-11 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-11 20:03 Precompiled Emacs binaries, where are the sources? Ulrich Mueller
2011-12-11 21:10 ` Christoph Scholtes [this message]
2011-12-11 21:33 ` Eli Zaretskii
2011-12-13 14:02   ` Chong Yidong

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EE51C54.2080503@gmail.com \
    --to=cschol2112@googlemail.com \
    --cc=emacs-devel@gnu.org \
    --cc=ulm@gentoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.