Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 7 Jun 2001 21:34:23 -0400 Message-Id: <200106080134.VAA06362@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj@envy.delorie.com using -f From: DJ Delorie To: ian@zembu.com CC: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com, cygwin@sources.redhat.com In-reply-to: (message from Ian Lance Taylor on 07 Jun 2001 18:31:08 -0700) Subject: Re: Another RFC: regex in libiberty References: <200106080127.VAA01308@greed.delorie.com> > gdb already ships with gnu-regex.c. Why not just move that to > libiberty? Because gdb, tcl, expect, cygwin, and gcc each have a copy of regex, and they're all different. Which to choose? > I can't see any reason for a BSD-licensed regex in libiberty. > libiberty already GPL code. Any regex added to libiberty becomes part of newlib and cygwin as well, and those projects are sensitive to GPL vs non-GPL licensing issues. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple