home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!gatech!concert!uvaarpa!murdoch!fermi.clas.Virginia.EDU!gsh7w
- From: gsh7w@fermi.clas.Virginia.EDU (Greg Hennessy)
- Subject: Re: [386bsd] GNU malloc in favor of BSD malloc in libc - shall we vote?
- Message-ID: <1992Dec31.232412.14996@murdoch.acc.Virginia.EDU>
- Sender: usenet@murdoch.acc.Virginia.EDU
- Organization: University of Virginia
- References: <JKH.92Dec31154004@whisker.lotus.ie> <1hvu79INNjqq@ftp.UU.NET>
- Date: Thu, 31 Dec 1992 23:24:12 GMT
- Lines: 18
-
- In article <1hvu79INNjqq@ftp.UU.NET> sef@Kithrup.COM (Sean Eric Fagan) writes:
- #GNU malloc is copylefted. Using it in a library means that every program
- #compiled using that library is copylefted. That is almost certainly the
- #reason why it is not used, and I cannot fault anyone for that.
-
- Well, this would mean that programs would have to be distributed under
- the less restrictive GLPL instead of the GPL, but I still bet many
- people won't like this restriction. People would be required to ship a
- linkable executable, but would not be forced to release source code.
-
-
-
-
- --
- -Greg Hennessy, University of Virginia
- USPS Mail: Astronomy Department, Charlottesville, VA 22903-2475 USA
- Internet: gsh7w@virginia.edu
- UUCP: ...!uunet!virginia!gsh7w
-