From: Arash Esbati <arash.esbati@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: phillip.lord@russet.org.uk, emacs-devel@gnu.org
Subject: Re: Emacs binaries for Windows
Date: Sat, 20 Aug 2016 17:49:45 +0200 [thread overview]
Message-ID: <86zio71luu.fsf@gmail.com> (raw)
In-Reply-To: <83vaywd4vi.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 19 Aug 2016 20:51:13 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Arash Esbati <arash.esbati@gmail.com>
>> Cc: emacs-devel@gnu.org
>> Date: Fri, 19 Aug 2016 18:33:06 +0200
>>
>> Thanks for your response. I try to give an example: Currently, Msys2
>> delivers a package named
>>
>> mingw-w64-x86_64-expat-2.1.1-1-any.pkg.tar.xz
>>
>> containing `libexpat-1.dll'. If you clon the repository from
>>
>> https://github.com/Alexpux/MINGW-packages.git
>>
>> and cd to `./MINGW-packages/mingw-w64-expat', the command
>>
>> makepkg-mingw --allsource -sLf
>>
>> downloads the original sources from
>>
>> https://downloads.sourceforge.net/expat/expat-2.1.1.tar.bz2
>>
>> and makes an archive
>>
>> mingw-w64-expat-2.1.1-1.src.tar.gz
>>
>> containing the archive from sourceforge and a Msys2 specific patch
>> called `001-fix-extension.patch' (plus PKGBUILD & .SRCINFO files).
>>
>> My first question is: With the provision made above, can the file
>> `libexpat-1.dll' be distributed along with an Emacs binary, which is
>> also built against this DLL file? (I will come back with a second
>> question later).
>
> IIUC, no. The sources are really on another server, so they could
> remove them, and your script will simply fail. The GPL requires that
> the binaries and the sources be either both available or both absent.
>
> Once again, the only practical way of complying with GPL is to provide
> the source archive from the same server as the binaries. (The GPL
> doesn't request that literally, but I know of no other scheme that
> really works.)
I see your point, and I'm seeking for a way to store library sources
next to Emacs binaries on the same server. I think we already have a
solution: the library sources can be packaged the way I have described;
if Phil agrees to go this route as well, he could package the sources
and upload them with the next RC which can be distributed with the
necessary DLLs.
Best, Arash
next prev parent reply other threads:[~2016-08-20 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 7:45 Emacs binaries for Windows Arash Esbati
2016-08-19 14:50 ` Eli Zaretskii
2016-08-19 16:33 ` Arash Esbati
2016-08-19 17:51 ` Eli Zaretskii
2016-08-19 20:27 ` Óscar Fuentes
2016-08-20 15:49 ` Arash Esbati [this message]
2016-08-20 15:58 ` Eli Zaretskii
2016-08-22 10:37 ` Phillip Lord
2016-08-22 14:54 ` Eli Zaretskii
2016-08-23 11:26 ` Phillip Lord
2016-08-23 14:35 ` Eli Zaretskii
2016-08-23 17:02 ` Arash Esbati
2016-08-23 17:21 ` Eli Zaretskii
2016-08-24 10:42 ` Phillip Lord
2016-08-19 15:03 ` Phillip Lord
2016-08-19 17:24 ` Arash Esbati
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=86zio71luu.fsf@gmail.com \
--to=arash.esbati@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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.