From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] libxml++: new package
Date: Wed, 24 Apr 2013 16:08:45 +0200 [thread overview]
Message-ID: <20130424160845.4677af42@skate> (raw)
In-Reply-To: <1366791236-22718-2-git-send-email-nicolas.menegale@openwide.fr>
Dear nmenegale,
On Wed, 24 Apr 2013 10:13:56 +0200, nmenegale wrote:
> +#############################################################
> +#
> +# LibXML++
> +#
> +#############################################################
One empty line between headers and variables.
> +LIBXMLPP_VERSION_MAJOR = 2.34
> +LIBXMLPP_VERSION_MINOR = 2
> +LIBXMLPP_VERSION = $(LIBXMLPP_VERSION_MAJOR).$(LIBXMLPP_VERSION_MINOR)
> +LIBXMLPP_LICENSE = LGPLv2+
License wise, this package is funky. The COPYING file contains the text
of LGPLv2.1. The source files of the library in the libxml++/ directory
just say "are covered by the GNU Lesser General Public License, which
should be included with libxml++ as the file COPYING." without
specifying the version, and whether is 'or later' or not.
And the examples in the examples/ directory are under "GNU Library
General Public License as published by the Free Software Foundation;
either version 2 of the License, or (at your option) any later
version.".
So this looks a package for which the licensing question was not really
handled properly. If we want to express what I found, it should
probably be something like:
LIBXMLPP_LICENSE = LGPLv2.1 (library), LGPLv2+ (examples)
LIBXMLPP_LICENSE_FILES = COPYING
But I am not sure this is actually the intention of the libxml++
authors.
> +LIBXMLPP_SOURCE = libxml++-$(LIBXMLPP_VERSION).tar.bz2
Use .tar.xz instead?
> +LIBXMLPP_SITE = http://ftp.gnome.org/pub/GNOME/sources/libxml++/$(LIBXMLPP_VERSION_MAJOR)
> +LIBXMLPP_INSTALL_STAGING = YES
> +LIBXMLPP_DEPENDENCIES = libxml2 glibmm host-pkgconf
> +
> +$(eval $(autotools-package))
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-24 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 8:13 [Buildroot] [PATCH 1/2] glibmm: new package nmenegale
2013-04-24 8:13 ` [Buildroot] [PATCH 2/2] libxml++: " nmenegale
2013-04-24 14:08 ` Thomas Petazzoni [this message]
2013-04-24 14:02 ` [Buildroot] [PATCH 1/2] glibmm: " Thomas Petazzoni
2013-04-24 14:03 ` Thomas Petazzoni
2013-04-24 19:43 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2013-04-24 15:11 nmenegale
2013-04-24 15:11 ` [Buildroot] [PATCH 2/2] libxml++: " nmenegale
2013-04-24 19:49 ` Peter Korsgaard
2013-04-23 14:09 [Buildroot] [PATCH 1/2] glibmm: " nmenegale
2013-04-23 14:09 ` [Buildroot] [PATCH 2/2] libxml++: " nmenegale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130424160845.4677af42@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.