Date: Thu, 12 Aug 1999 09:32:13 -0700 (PDT) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: green@FreeBSD.ORG (Brian F. Feldman) Cc: imp@village.org (Warner Losh), hackers@FreeBSD.ORG Subject: Re: libcompat proposition Message-ID: <199908121632.JAA26032@troutmask.apl.washington.edu> In-Reply-To: <Pine.BSF.4.10.9908121122040.90630-100000@janus.syracuse.net> from "Brian F. Feldman" at "Aug 12, 1999 11:22:53 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Brian F. Feldman wrote: > On Wed, 11 Aug 1999, Warner Losh wrote: > > > In message <Pine.BSF.4.10.9908112337400.81521-100000@janus.syracuse.net> "Brian F. Feldman" writes: > > : What do you all think about growing a gnu subdirectory in src/lib/libcompat? > > : Things like a getopt_long implementation (yes, if it will be accepted, > > : I am volunteering to write it...) would go there, and all sorts of lame > > : GNU libc cruft that we can try to be more compatible with. > > > > src/gnu/lib/libgnucompat > > > > might be better if is was GPL code. We've been trying to keep GPL'd > > code walled off from other code in the system. > > I'd be rewriting the code to make it freed, and put it in libcompat/gnu. I > wouldn't be taking encumbered code to put in a standard library that would > normally be free... > If you're writing unencumbered code, placing it under libcompat/gnu may lead to confusion because all other directory paths containing gnu contain GPL'd code. Just stick it into libcompat. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908121632.JAA26032>