From: Eli Zaretskii <eliz@gnu.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: help-emacs-windows@gnu.org, emacs-devel@gnu.org
Subject: Re: [h-e-w] emacs-20110510 windows binaries
Date: Fri, 13 May 2011 09:04:35 +0300 [thread overview]
Message-ID: <838vubgmq4.fsf@gnu.org> (raw)
In-Reply-To: <877h9vzqws.fsf@lifelogs.com>
> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Thu, 12 May 2011 13:59:15 -0500
> Cc: help-emacs-windows@gnu.org
>
> JB> And, IIUC, distributing the binary DLLs means making also the code
> JB> accesible, doesn't it?
>
> The GnuTLS code is accessible at git://git.savannah.gnu.org/gnutls.git
>
> It doesn't have to be distributed with the binaries IIUC, but a link to
> the source code should be provided.
No, that's not enough. This issue came up before, and the conclusion
was always that the sources that were used to compile the binaries
should be readily available, which in practice means we need to
provide the sources near the binaries.
next prev parent reply other threads:[~2011-05-13 6:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 18:10 emacs-20110510 windows binaries Sean Sieger
2011-05-12 13:03 ` Ted Zlatanov
2011-05-12 13:41 ` Juanma Barranquero
2011-05-12 14:39 ` Ted Zlatanov
2011-05-12 15:01 ` [h-e-w] " Juanma Barranquero
2011-05-12 17:03 ` Ted Zlatanov
2011-05-12 18:47 ` Juanma Barranquero
2011-05-12 18:59 ` Ted Zlatanov
2011-05-12 19:29 ` Juanma Barranquero
2011-05-13 6:04 ` Eli Zaretskii [this message]
2011-05-13 14:50 ` Ted Zlatanov
2011-05-13 16:25 ` Sean Sieger
2011-05-12 19:27 ` Drew Adams
2011-05-12 19:33 ` Ted Zlatanov
2011-05-12 16:51 ` Sean Sieger
2011-05-13 2:18 ` Christoph Scholtes
2011-05-13 10:51 ` Juanma Barranquero
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=838vubgmq4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=help-emacs-windows@gnu.org \
--cc=tzz@lifelogs.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 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.