openembedded-core.git/meta/recipes-extended/groff, branch pyro

groff: replace "perl -w" with "use warnings"

2017-04-08T21:48:05+00:00

The shebang's max length is usually 128 as defined in
/usr/include/linux/binfmts.h:
  #define BINPRM_BUF_SIZE 128

There would be errors when @PERL@ (hostools/perl) is longer than 128,
use '/usr/bin/env perl' can fix the problem, but '/usr/bin/env perl -w'
doesn't work:

/usr/bin/env: perl -w: No such file or directory

So replace "perl -w" with "use warnings" to make it work.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

recipes: Move out stale GPLv2 versions to a seperate layer

2017-03-07T20:04:58+00:00

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

groff: not ship /usr/bin/glilypond

2016-09-19T08:02:20+00:00

Not ship /usr/bin/glilypond and related files such
as man file /usr/share/man/man1/glilypond.1 and other
three files related to glilypond under
/usr/lib/groff/glilypond in embedded system, it is because:

- Remove the confusion about glilypond fails to run
  because it lacks dependency on File::HomeDir perl
  module

- We don't often have need for sheet music conversion
  in groff in embedded or IoT devices (glilypond
  transforms sheet music written in the lilypond language
  into the groff language using the .PSPIC request, such
  that groff can transform it into a format that can be
  displayed directly).

Signed-off-by: Mingli Yu 
Signed-off-by: Richard Purdie

groff: correct the location path for awk

2016-08-25T22:02:48+00:00

awk is located at /usr/bin/, but not /bin/

Signed-off-by: Zhenbo Gao 
Signed-off-by: Ross Burton

groff_1.18.1.4: fix narrowing conversion error

2016-08-03T11:59:49+00:00

While gcc6 used, build old groff (for anti-GPLv3 reasons) failed:
.....
|groff-1.18.1.4/src/devices/grolbp/charset.h:69:1: error: narrowing
conversion of '130' from 'int' to 'char' inside { } [-Wnarrowing]
......

In upstream git://git.savannah.gnu.org/groff.git,
the following commit fix the issue, but the license is GPLV3,
we could not backport it to the old groff which license is GPLV2.
...
commit d180038ae0da19655bc2760ae2043efa0550a76c
Author: Werner LEMBERG 
Date:   Wed Apr 16 21:11:07 2003 +0000
    * src/devices/grolbp/charset.h (symset): Use `unsigned char'.
...

We use another different way to fix the issue.

[YOCTO #9896]

Signed-off-by: Hongxu Jia 
Signed-off-by: Ross Burton

meta: Fix Upstream-Status statements

2015-09-12T21:59:01+00:00

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

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

Use die() or bbfatal_log() where the log should definitely be printed

2015-07-16T14:08:45+00:00

Change calls to bbfatal() to either die() or bbfatal_log() where we know
we want the full log to be printed by the UI (calling bberror or bbfatal
would otherwise suppress it since the change to connect these functions
through to the UI.) bbfatal() is still fine to use where there is enough
context information in the message such that the log isn't needed.

Signed-off-by: Paul Eggleton

recipes: Fix charset.alias for musl

2015-04-21T06:19:05+00:00

This is same gnulib fix replicated across needed recipes

Change-Id: I756713407111a726eae98e26c9c1ff64981371c0
Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

groff: fix RDEPENDS

2015-04-19T12:34:04+00:00

RDEPENDS_${PN} is appended with "sed" and on the following line it's fixed
to just "perl". Merge both lines to have correct RDEPENDS.

Signed-off-by: Dmitry Eremin-Solenikov 
Signed-off-by: Richard Purdie

groff: add runtime dependency on sed

2015-04-13T21:28:35+00:00

This is to suppress the following QA warning:
groff-1.22.2: groff requires /bin/sed, but no providers in its RDEPENDS [file-rdeps]

Signed-off-by: Dmitry Eremin-Solenikov 
Signed-off-by: Richard Purdie