Mail Archives: djgpp/1996/03/20/22:03:39
Xref: | news2.mv.net comp.os.msdos.djgpp:1997
|
From: | agserm AT netwizards DOT net (Ansel Sermersheim)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Could somebody clarify the FSF license?
|
Date: | Sun, 17 Mar 1996 03:19:50 GMT
|
Organization: | West Coast Online's News Server - Not responsible for content
|
Lines: | 29
|
Message-ID: | <4ig07m$pu6@news.wco.com>
|
Reply-To: | agserm AT netwizards DOT net
|
NNTP-Posting-Host: | dial26.netwizards.net
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
I've been wondering if somebody can help me understand the FSF
license. First, I would like it if somebody could help me figure out
what libraries are included under it (and hence would bring my entire
product under it), and I'd like to know what it allows me to do.
I have no problem with making the source available to anyone who
requests it, but I can't figure out if it allows me to charge. Tell
me if this arrangement is possible:
A shareware version which may be freely distributed, and anyone can
get the source to.
A registered version which you must pay for, and anyone who registers
can get the source to.
Actually, I guess that having the reg. ver code avail to everybody
wouldn't be too disastrous, but I will have to avoid the libs which
are most useful if I cannot charge for the registered ver .exe
(Figuring that not many people will have the ability or inclination to
download djgpp and compile the program just to save a lousy $15)
TIA very much.
P.S. I finally figured out after 3 days trying to get gcc to work that
set djgpp=e:\djgpp\djgpp.env
does not equal
set djgpp = e:\djgpp\djgpp.env
Arrgh!
(I like the compiler a lot though)
- Raw text -