This software contains an older or slightly modified BSD license in
its COPYING file and assigns copyright to the specific authors. The
code (see the About function) makes it clear that a BSD
license is intended:
"license", xfce_get_license_text (XFCE_LICENSE_TEXT_BSD),
Signed-off-by: Ash Charles <ashcharles@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Like several other xfce plugins, this software contains an older or
slightly modified BSD license in its COPYING file and assigns copyright
to the specific authors. The code itself (see the xfce_xkb_about
function) however makes it clear that a GPL license is intended:
xfce_get_license_text (XFCE_LICENSE_TEXT_GPL));
Use GPLv2, not the author's name, as the LICENSE matching other plugins
with the same license text.
Signed-off-by: Ash Charles <ashcharles@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This software contains an older or slightly modified BSD license in
its COPYING file and assigns copyright to the specific authors. The
code (see the wavelan_show_about function) makes it clear that a BSD
license is intended:
"license", xfce_get_license_text (XFCE_LICENSE_TEXT_BSD),
(caveat: and of course, INAL)
Signed-off-by: Ash Charles <ashcharles@gmail.com>
Acked-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* the COPYING file looks more like slightly modified BSD license and BenediktMeurer, FlorianRivoal
are just names of Copyright holders, but I'll leave that to recipe maintainer
fixes:
WARNING: Recipe xfce4-wavelan-plugin, LICENSE (BenediktMeurer FlorianRivoal)
has invalid format, LICENSES must have operator "([&|() ])" between them.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
see [1] for more information
https://bugzilla.xfce.org/show_bug.cgi?id=10916
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
detected in Martin's world with test-dependencies
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Changes:
- rename SUMMARY with length > 80 to DESCRIPTION
- rename DESCRIPTION with length < 80 to (non present tag) SUMMARY
- drop final point character at the end of SUMMARY string
- remove trailing whitespace of SUMMARY line
Note: don't bump PR
Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
fixes (detected in Martin's) world build:
| configure:14617: checking for libsoup-2.4 >= 2.26.0
| configure:14659: result: not found
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
It's not necessary to specify the protocol parameter when it's the
default protocol for the fetcher, e.g. the default protocol for
git fetcher it git, "protocol=git" isn't needed.
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
In 7b35cdc554ee3f42f9619996604d4674126711c1 xfce4-settings was updated to
development-release 4.11.0. Reason for this was handling of keyboard layout
by xfce4-settings.
With this patch xfce4-xkb-plugin synchronizes with xfce4-settings, shares
settings and uses dialogs from xfce4-settings. These changes were not yet
released because they depend on development-release of xfce4-settings.
Next stable release of xfce4-settings will be with xfce 4.12 with release date
unknown [1].
[1] http://wiki.xfce.org/releng/4.12/roadmap#roadmapplanned_features
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
I do not have the environment and the time to create a tarball, so take sources
from my git repo.
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
