This is the mail archive of the firstname.lastname@example.org
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: [ANN] Cygwin DEV survey
- To: email@example.com
- Subject: Re: [ANN] Cygwin DEV survey
- From: DJ Delorie <firstname.lastname@example.org>
- Date: Sun, 7 Mar 1999 20:24:28 -0500
- CC: N8TM@aol.com, email@example.com, firstname.lastname@example.org
- Delivered-To: email@example.com
- Delivered-To: mailing list firstname.lastname@example.org
- In-reply-to: <36E311C7.672E@uni-duesseldorf.de> (message from Stipe Tolj onMon, 08 Mar 1999 00:54:47 +0100)
- Mailing-List: contact email@example.com; run by ezmlm
- References: <firstname.lastname@example.org> <199903072222.RAA14720@envy.delorie.com> <36E311C7.672E@uni-duesseldorf.de>
- Sender: email@example.com
> > Besides, it doesn't matter if it's easy or not. The GPL is a legal ...
> of course you are right. But this may be considered as an optimal
> solution that doesn't match reality in some cases, like normal life
Yup. For a lot of people it's not practical to write a custom license
for a package. The GPL is a good license for a lot of situations, and
it's been thoroughly reviewed by lawyers already, so a lot of people
just adopt it as-is. Unfortunately, a lot of people adopt it without
fully understanding it. That doesn't mean that you can ignore it
because it's inconvenent.
> In my opinion not a very representative example for our aims :)
No, but one example is enough to explain the GPL.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org