The New Plan

ebuild branch has old ebuilds.  profiles dir still has CFLAGS.

Everything else is removed or modified for changing of upstream to
Alpine.

1 files changed, 0 insertions, 62 deletions

diff --git a/licenses/lcc b/licenses/lcc
deleted file mode 100644
index 0a79cb853..000000000
--- a/licenses/lcc
+++ /dev/null
@@ -1,62 +0,0 @@
-The authors of this software are Christopher W. Fraser and
-David R. Hanson.
-
-Copyright (c) 1991,1992,1993,1994,1995,1996,1997,1998 by AT&T,
-Christopher W. Fraser, and David R. Hanson. All Rights Reserved.
-
-Permission to use, copy, modify, and distribute this software for any
-purpose, subject to the provisions described below, without fee is
-hereby granted, provided that this entire notice is included in all
-copies of any software that is or includes a copy or modification of
-this software and in all copies of the supporting documentation for
-such software.
-
-THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED
-WARRANTY. IN PARTICULAR, NEITHER THE AUTHORS NOR AT&T MAKE ANY
-REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY
-OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
-
-
-lcc is not public-domain software, shareware, and it is not protected
-by a `copyleft' agreement, like the code from the Free Software
-Foundation.
-
-lcc is available free for your personal research and instructional use
-under the `fair use' provisions of the copyright law. You may, however,
-redistribute lcc in whole or in part provided you acknowledge its
-source and include this CPYRIGHT file. You may, for example, include
-the distribution in a CDROM of free software, provided you charge only
-for the media, or mirror the distribution files at your site.
-
-You may not sell lcc or any product derived from it in which it is a
-significant part of the value of the product. Using the lcc front end
-to build a C syntax checker is an example of this kind of product.
-
-You may use parts of lcc in products as long as you charge for only
-those components that are entirely your own and you acknowledge the use
-of lcc clearly in all product documentation and distribution media. You
-must state clearly that your product uses or is based on parts of lcc
-and that lcc is available free of charge. You must also request that
-bug reports on your product be reported to you. Using the lcc front
-end to build a C compiler for the Motorola 88000 chip and charging for
-and distributing only the 88000 code generator is an example of this
-kind of product.
-
-Using parts of lcc in other products is more problematic. For example,
-using parts of lcc in a C++ compiler could save substantial time and
-effort and therefore contribute significantly to the profitability of
-the product. This kind of use, or any use where others stand to make a
-profit from what is primarily our work, requires a license agreement
-with Addison-Wesley.  Per-copy and unlimited use licenses are
-available; for more information, contact
-
-	J. Carter Shanklin
-	Addison Wesley Longman, Inc. 
-	2725 Sand Hill Rd.
-	Menlo Park, CA 94025
-	650/854-0300 x2478 FAX: 650/614-2930 jcs@awl.com
------
-Chris Fraser / cwfraser@microsoft.com
-David Hanson / drh@microsoft.com
-$Revision: 1.1 $ $Date: 2013/04/28 22:21:08 $
-