From owner-freebsd-hackers Thu Aug 12 9:28:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id A46A015040; Thu, 12 Aug 1999 09:28:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id JAA26032; Thu, 12 Aug 1999 09:32:13 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199908121632.JAA26032@troutmask.apl.washington.edu> Subject: Re: libcompat proposition In-Reply-To: from "Brian F. Feldman" at "Aug 12, 1999 11:22:53 am" To: green@FreeBSD.ORG (Brian F. Feldman) Date: Thu, 12 Aug 1999 09:32:13 -0700 (PDT) Cc: imp@village.org (Warner Losh), hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian F. Feldman wrote: > On Wed, 11 Aug 1999, Warner Losh wrote: > > > In message "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