These are recipes where the upstream has moved to GPLv3 and these old
versions are the last ones under the GPLv2 license.

There are several reasons for making this move. There is a different
quality of service with these recipes in that they don't get security
fixes and upstream no longer care about them, in fact they're actively
hostile against people using old versions. The recipes tend to need a
different kind of maintenance to work with changes in the wider ecosystem
and there needs to be isolation between changes made in the v3 versions
and those in the v2 versions.

There are probably better ways to handle a "non-GPLv3" system but right
now having these in OE-Core makes them look like a first class citizen
when I believe they have potential for a variety of undesireable issues.

Moving them into a separate layer makes their different needs clearer, it
also makes it clear how many of these there are. Some are probably not
needed (e.g. mc), I also wonder whether some are useful (e.g. gmp)
since most things that use them are GPLv3 only already. Someone could
now more clearly see how to streamline the list of recipes here.

I'm proposing we mmove to this separate layer for 2.3 with its future
maintinership and testing to be determined in 2.4 and beyond.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

It has been built but not installed by default, while 1.11 builds and
installs it.

Fixed when build non_gplv3 + perl:
powerpc64-wrs-linux-gcc -m64 -mhard-float -mcpu=e6500
--sysroot=/mnt/docker/test_p/bitbake_build/tmp/sysroots/fsl-t2xxx
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -
fstack-protector -shared NDBM_File.o  -o
../../lib/auto/NDBM_File/NDBM_File.so   \
   -lgdbm -lgdbm_compat         \

ld: cannot find -lgdbm_compat
collect2: error: ld returned 1 exit status
Makefile:473: recipe for target '../../lib/auto/NDBM_File/NDBM_File.so' failed

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>

Fix a variety of problems such as typos, bad punctuations, or incorrect
Upstream-Status values.

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

There are gdbm 1.8.3 and gdbm 1.11, while 1.8.3 is GPLv2, it should
install ndbm.h and dbm.h as what 1.11 does, to make perl build OK when
non-gplv3 build.

Fixed when perl build: (non-gplv3 buld)
| NDBM_File.xs:18:60: fatal error: gdbm/ndbm.h: No such file or directory
|  #  include <gdbm/ndbm.h> /* RedHat compatibility version */
|                                                             ^
| compilation terminated.

And:
| ODBM_File.xs:8:19: fatal error: dbm.h: No such file or directory
|  #  include <dbm.h>
|                    ^
| compilation terminated.

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Signed-off-by: Christopher Larson <chris_larson@mentor.com>

Install gdbm test-suite and run it as ptest

Signed-off-by: Maxin B. John <maxin.john@enea.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>

The class itself currently does nothing. The idea is to mark all recipes that
make use of the texinfo utilities. In the future, this class could be used to
suppress the generation/formatting of documentation for performance,
explicitly track dependencies on these utilities, and eliminate Yocto's
current dependency on the host system's texinfo utilities.

Signed-off-by: Max Eliaser <max.eliaser@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Signed-off-by: Saul Wold <sgw@linux.intel.com>

A lot of our recipes had short one-line DESCRIPTION values and no
SUMMARY value set. In this case it's much better to just set SUMMARY
since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY
is at least useful. I also took the opportunity to fix up a lot of the
new SUMMARY values, making them concisely explain the function of the
recipe / package where possible.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>