public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steve Morris <smorris@nexen.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: [ANN] Cygwin DEV survey
Date: Tue, 09 Mar 1999 08:47:00 -0000	[thread overview]
Message-ID: <199903091647.LAA05285@brocade.nexen.com> (raw)
In-Reply-To: < 36E4C5C5.B27DD935@classic-games.com >

Greg Miller writes:
 > DJ Delorie wrote:
 > > The reason I specified full sources for all application is because
 > > when you build an application with cygwin, the resulting binary always
 > > includes sources from cygwin (namely, the startup code and import
 > > library stubs), so all applications thus compiled must be distributed
 > > under the terms of the GPL.
 > 
 > Possibly. American courts have *sometimes* held that, for purposes of
 > interoperation with other software and/or hardware, you can ignore
 > licensing terms/copyrights that would prevent that interoperation. Has
 > the GPL ever been tested in an appeals court for Windows .DLLs and the
 > associated .LIB files? If not, we're guessing what would happen.

Hmmm... To expand a little the mentioned rulings might suggest that
one has the right to distribute software that will run under cygwin
even if it means using some otherwise copy protected software. As an
example Microsoft can't restrict the use of code that is required to
write a Windows application, even if they hold the copyright on that
code.

If this were applicable it would mean that Cygnus does not have the
right to restrict distribution of code that runs under Cygwin by
restricting the inclusion of copyrighted code necessary to run under
cygwin. This would suggest that while Cygnus has the right to control
and restrict cygwin itself it cannot similarly control the glue
required to run under cygwin.

Of course cygwin is not Windows. Restricting distribution of software
running under a monopoly environment like Windows is a lot different
than restricting the distribution of cygwin computable software. The
courts might rule differently in these two cases. There are legitimate
alternatatives to cygwin in the UNIX apps on Windows market. The
courts would probably find that relevent.

All I know is that if I ever wanted to do binary distribution of
cygwin applications (i.e. not under GPL) I would buy a license from
Cygnus. It is probably cheaper than the lawyers fees to figure this
out. I would rather Cygnus get the money than the lawyers.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: Steve Morris <smorris@nexen.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: [ANN] Cygwin DEV survey
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <199903091647.LAA05285@brocade.nexen.com> (raw)
Message-ID: <19990331194500.ZoArGdurxSG9Wuv0ckvZIexMSsRxY4b39FS5oD3DCbY@z> (raw)
In-Reply-To: <36E4C5C5.B27DD935@classic-games.com>

Greg Miller writes:
 > DJ Delorie wrote:
 > > The reason I specified full sources for all application is because
 > > when you build an application with cygwin, the resulting binary always
 > > includes sources from cygwin (namely, the startup code and import
 > > library stubs), so all applications thus compiled must be distributed
 > > under the terms of the GPL.
 > 
 > Possibly. American courts have *sometimes* held that, for purposes of
 > interoperation with other software and/or hardware, you can ignore
 > licensing terms/copyrights that would prevent that interoperation. Has
 > the GPL ever been tested in an appeals court for Windows .DLLs and the
 > associated .LIB files? If not, we're guessing what would happen.

Hmmm... To expand a little the mentioned rulings might suggest that
one has the right to distribute software that will run under cygwin
even if it means using some otherwise copy protected software. As an
example Microsoft can't restrict the use of code that is required to
write a Windows application, even if they hold the copyright on that
code.

If this were applicable it would mean that Cygnus does not have the
right to restrict distribution of code that runs under Cygwin by
restricting the inclusion of copyrighted code necessary to run under
cygwin. This would suggest that while Cygnus has the right to control
and restrict cygwin itself it cannot similarly control the glue
required to run under cygwin.

Of course cygwin is not Windows. Restricting distribution of software
running under a monopoly environment like Windows is a lot different
than restricting the distribution of cygwin computable software. The
courts might rule differently in these two cases. There are legitimate
alternatatives to cygwin in the UNIX apps on Windows market. The
courts would probably find that relevent.

All I know is that if I ever wanted to do binary distribution of
cygwin applications (i.e. not under GPL) I would buy a license from
Cygnus. It is probably cheaper than the lawyers fees to figure this
out. I would rather Cygnus get the money than the lawyers.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  parent reply	other threads:[~1999-03-09  8:47 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-07  9:11 Stipe Tolj
     [not found] ` < 36E2B26B.BEA9DC67@uni-duesseldorf.de >
1999-03-07 10:06   ` DJ Delorie
     [not found]     ` < 199903071805.NAA13212@envy.delorie.com >
1999-03-07 11:10       ` Michael Hirmke
     [not found]         ` < 7COu0ETppfB@mike.franken.de >
1999-03-07 12:53           ` DJ Delorie
1999-03-07 15:55             ` Stipe Tolj
1999-03-31 19:45               ` Stipe Tolj
1999-03-31 19:45             ` DJ Delorie
1999-03-07 15:55         ` Stipe Tolj
     [not found]           ` < 36E30E97.7310@uni-duesseldorf.de >
1999-03-07 16:11             ` Tripp Lilley
1999-03-31 19:45               ` Tripp Lilley
1999-03-07 17:16             ` DJ Delorie
1999-03-31 19:45               ` DJ Delorie
1999-03-31 19:45           ` Stipe Tolj
1999-03-31 19:45         ` Michael Hirmke
1999-03-07 15:54     ` Stipe Tolj
     [not found]       ` < 36E30CB6.1B5F@uni-duesseldorf.de >
1999-03-07 16:41         ` Chris Faylor
1999-03-31 19:45           ` Chris Faylor
1999-03-07 17:13         ` DJ Delorie
1999-03-08 22:58           ` Greg Miller
     [not found]             ` < 36E4C5C5.B27DD935@classic-games.com >
1999-03-09  8:47               ` Steve Morris [this message]
1999-03-09 11:48                 ` Greg Miller
1999-03-31 19:45                   ` Greg Miller
1999-03-31 19:45                 ` Steve Morris
1999-03-31 19:45             ` Greg Miller
1999-03-09 17:39           ` Stipe Tolj
     [not found]             ` < 36E5C12D.5017@uni-duesseldorf.de >
1999-03-09 17:42               ` DJ Delorie
1999-03-31 19:45                 ` DJ Delorie
1999-03-31 19:45             ` Stipe Tolj
1999-03-31 19:45           ` DJ Delorie
1999-03-08  7:14         ` Michael Weiser
     [not found]           ` < 36e38cb6.1308201@mail.weiser.saale-net.de >
1999-03-08  7:20             ` DJ Delorie
1999-03-31 19:45               ` DJ Delorie
1999-03-09 17:40           ` Stipe Tolj
1999-03-31 19:45             ` Stipe Tolj
1999-03-31 19:45           ` Michael Weiser
1999-03-31 19:45       ` Stipe Tolj
     [not found]     ` <199903081523.KAA03738@brocade.nexen.com>
1999-03-08  7:34       ` DJ Delorie
     [not found]         ` <87yal7dgkn.fsf@mattdav.vip.best.com>
1999-03-08 10:06           ` DJ Delorie
     [not found]             ` < 199903081805.NAA22437@envy.delorie.com >
1999-03-08 11:48               ` Steve Morris
1999-03-31 19:45                 ` Steve Morris
1999-03-31 19:45             ` DJ Delorie
1999-03-31 19:45         ` DJ Delorie
1999-03-31 19:45     ` DJ Delorie
1999-03-31 19:45 ` Stipe Tolj
1999-03-07  9:19 Suhaib M. Siddiqi
     [not found] ` < 007501be68c0$ee6d69b0$29acdfd0@InspirePharm.Com >
1999-03-07 10:07   ` DJ Delorie
1999-03-31 19:45     ` DJ Delorie
1999-03-07 10:11   ` Tripp Lilley
1999-03-07 15:54     ` Stipe Tolj
1999-03-31 19:45       ` Stipe Tolj
1999-03-31 19:45     ` Tripp Lilley
1999-03-31 19:45 ` Suhaib M. Siddiqi
1999-03-07 10:13 Suhaib M. Siddiqi
1999-03-31 19:45 ` Suhaib M. Siddiqi
1999-03-07 14:08 N8TM
     [not found] ` < 57b99220.36e2f890@aol.com >
1999-03-07 14:22   ` DJ Delorie
1999-03-07 15:55     ` Stipe Tolj
     [not found]       ` < 36E311C7.672E@uni-duesseldorf.de >
1999-03-07 17:25         ` DJ Delorie
1999-03-31 19:45           ` DJ Delorie
1999-03-31 19:45       ` Stipe Tolj
1999-03-31 19:45     ` DJ Delorie
1999-03-31 19:45 ` N8TM
1999-03-07 15:52 Suhaib M. Siddiqi
1999-03-31 19:45 ` Suhaib M. Siddiqi
1999-03-07 19:09 Earnie Boyd
1999-03-31 19:45 ` Earnie Boyd
1999-03-08  2:33 Smith, Martin
1999-03-09 17:40 ` Stipe Tolj
1999-03-31 19:45   ` Stipe Tolj
1999-03-31 19:45 ` Smith, Martin
1999-03-08  5:50 Earnie Boyd
1999-03-09 17:40 ` Stipe Tolj
     [not found]   ` < 36E5C95D.7810@uni-duesseldorf.de >
1999-03-10  7:18     ` Michael Weiser
     [not found]       ` < 36e94a87.1879752@mail.weiser.saale-net.de >
1999-03-10  7:44         ` DJ Delorie
     [not found]           ` < 199903101543.KAA07228@envy.delorie.com >
1999-03-10 18:33             ` Michael Weiser
1999-03-31 19:45               ` Michael Weiser
1999-03-31 19:45           ` DJ Delorie
1999-03-11  0:15       ` Greg Miller
1999-03-31 19:45         ` Greg Miller
1999-03-11 15:59       ` Stipe Tolj
     [not found]         ` < 36E70E49.4A77@uni-duesseldorf.de >
1999-03-12  7:10           ` Michael Weiser
1999-03-31 19:45             ` Michael Weiser
1999-03-31 19:45         ` Stipe Tolj
1999-03-31 19:45       ` Michael Weiser
1999-03-31 19:45   ` Stipe Tolj
1999-03-31 19:45 ` Earnie Boyd
1999-03-08  6:58 Smith, Martin
1999-03-09 17:40 ` Stipe Tolj
1999-03-31 19:45   ` Stipe Tolj
1999-03-31 19:45 ` Smith, Martin
1999-03-10 18:46 Suhaib M. Siddiqi
1999-03-31 19:45 ` Suhaib M. Siddiqi
1999-03-11  5:30 Earnie Boyd
1999-03-31 19:45 ` Earnie Boyd
1999-03-11  6:07 Jonathan Pryor
1999-03-11 16:42 ` Stipe Tolj
1999-03-31 19:45   ` Stipe Tolj
1999-03-31 19:45 ` Jonathan Pryor

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=199903091647.LAA05285@brocade.nexen.com \
    --to=smorris@nexen.com \
    --cc=cygwin@sourceware.cygnus.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).