From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: system lags and dysfunctional after cygwin update
Date: Fri, 13 May 2016 16:56:00 -0000 [thread overview]
Message-ID: <4A4DC8BF-E3F6-40B1-AE69-D2E08A412757@etr-usa.com> (raw)
In-Reply-To: <f290f3cc-ce78-ccf1-0cb3-cdecdc9d7d4b@cygwin.com>
On May 13, 2016, at 10:41 AM, Yaakov Selkowitz wrote:
>
> On 2016-05-13 10:38, Warren Young wrote:
>
>> But after taking a peek at the AST license, it’s pretty clear it’s incompatible
>> with the GPL.
>
> True, but it is Open Source and therefore would be acceptable.
It depends on what “it” is.
The old AT&T AST license was most definitely not acceptable, requiring written acceptance of the license in order to transfer the source code. You may remember the clickthrough license on the old AT&T AST site. That’s fine for AT&T, but it doesn’t let Cygwin distribute source packages, for example.
There are other onerous terms in the AST license, too, such as a requirement that you tell AT&T in writing any time you made a patch to their software. Thus if it doesn’t build OOTB on Cygwin, we couldn’t distribute it in binary-only form, either.
All of that apparently went away at some point, though, because the header comment in a few of the ksh source files I looked at say it’s under the Eclipse Public License now:
https://github.com/att/ast
The old AST wasn’t even compatible with GitHub — no explicit license acceptance on git clone — but I think we can trust that as an official distribution of the ksh source code, since AT&T themselves link to the GitHub repo from here:
http://www.research.att.com/software_tools
So never mind, I think we’re in the clear here. But IANAL.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-05-13 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 14:36 Ben Altman
2016-05-12 14:44 ` Marco Atzeri
2016-05-12 15:20 ` Ben Altman
2016-05-13 2:20 ` Andrey Repin
2016-05-13 3:09 ` Ben Altman
[not found] ` <e864d93f-689f-fe75-f1bf-4777524ea022@gmail.com>
2016-05-12 15:37 ` Marco Atzeri
2016-05-12 15:57 ` Warren Young
2016-05-13 14:02 ` Ben Altman
2016-05-13 14:54 ` Marco Atzeri
2016-05-13 15:38 ` Warren Young
2016-05-13 16:41 ` Yaakov Selkowitz
2016-05-13 16:56 ` Warren Young [this message]
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=4A4DC8BF-E3F6-40B1-AE69-D2E08A412757@etr-usa.com \
--to=wyml@etr-usa.com \
--cc=cygwin@cygwin.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.
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).