kumquat-buildroot/package/libite/libite.mk

################################################################################
#
# libite
#
################################################################################

LIBITE_VERSION = 2.0.2
LIBITE_SITE = $(call github,troglobit,libite,v$(LIBITE_VERSION))
LIBITE_LICENSE = MIT, X11, ISC, BSD-2-Clause
LIBITE_LICENSE_FILES = LICENSE src/chomp.c src/pidfile.c
LIBITE_INSTALL_STAGING = YES
LIBITE_AUTORECONF = YES

$(eval $(autotools-package))
libite: new package Signed-off-by: Ryan Coe <bluemrp9@gmail.com> [Thomas: - rewrap Config.in help text - improve license description] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2016-10-13 05:42:45 +02:00			`################################################################################`
			`#`
			`# libite`
			`#`
			`################################################################################`

package: remove 'v' prefix from github-fetched packages On Github, a large number of projects name their tag vXYZ (i.e v3.0, v0.1, etc.). In some packages we do: <pkg>_VERSION = v0.3 <pkg>_SITE = $(call github foo,bar,$(<pkg>_VERSION)) And in some other packages we do: <pkg>_VERSION = 0.3 <pkg>_SITE = $(call github foo,bar,v$(<pkg>_VERSION)) I.e in one case we consider the version to be v0.3, in the other case we consider 0.3 to be the version. The problem with v0.3 is that when used in conjunction with release-monitoring.org, it doesn't work very well, because release-monitoring.org has the concept of "version prefix" and using that they drop the "v" prefix for the version. Therefore, a number of packages in Buildroot have a version that doesn't match with release-monitoring.org because Buildroot has 'v0.3' and release-monitoring.org has '0.3'. Since really the version number of 0.3, is makes sense to update our packages to drop this 'v'. This commit only addresses the (common) case of github packages where the prefix is simply 'v'. Other cases will be handled by separate commits. Also, there are a few cases that couldn't be handled mechanically that aren't covered by this commit. Signed-off-by: Victor Huesca <victor.huesca@bootlin.com> [Arnout: don't change flatbuffers, json-for-modern-cpp, libpagekite, python-scapy3k, softether] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> 2019-06-12 08:42:06 +02:00			`LIBITE_VERSION = 2.0.2`
			`LIBITE_SITE = $(call github,troglobit,libite,v$(LIBITE_VERSION))`
boot, package: use SPDX short identifier for BSD-2c We want to use SPDX identifier for license string as much as possible. SPDX short identifier for BSD-2c is BSD-2-Clause. This change is done using following command. find . -name "*.mk" \| xargs sed -ri '/LICENSE( )?[\+:]?=/s/BSD-2c/BSD-2-Clause/g' Signed-off-by: Rahul Bedarkar <rahulbedarkar89@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2017-03-30 15:43:39 +02:00			`LIBITE_LICENSE = MIT, X11, ISC, BSD-2-Clause`
libite: update path for license files Two of the license files have moved in the source package. Update the package to reflect these changes. Fixes: http://autobuild.buildroot.net/results/8fd71513f021652a9a4ff2354dd5fe4fedf3d557 http://autobuild.buildroot.net/results/6a1ab663f1093351662ca7b86c9224a630798f35 http://autobuild.buildroot.net/results/066373da2da2cc8c0c22cc4a3048d1b187c9c389 http://autobuild.buildroot.net/results/edad6ac5d3f61257e99b90c6f54d4d6786aa7ad7 http://autobuild.buildroot.net/results/c2b72c2a32de949a5b1ab46d6d7c540353cfaf5e http://autobuild.buildroot.net/results/8635ca4bbec464d196846a4018d1228d6651b211 Signed-off-by: Ryan Coe <bluemrp9@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> 2018-02-21 15:17:36 +01:00			`LIBITE_LICENSE_FILES = LICENSE src/chomp.c src/pidfile.c`
libite: new package Signed-off-by: Ryan Coe <bluemrp9@gmail.com> [Thomas: - rewrap Config.in help text - improve license description] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2016-10-13 05:42:45 +02:00			`LIBITE_INSTALL_STAGING = YES`
			`LIBITE_AUTORECONF = YES`

			`$(eval $(autotools-package))`