69808c7536
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>
17 lines
523 B
Makefile
17 lines
523 B
Makefile
################################################################################
|
|
#
|
|
# libcoap
|
|
#
|
|
################################################################################
|
|
|
|
LIBCOAP_VERSION = 4.1.2
|
|
LIBCOAP_SITE = $(call github,obgm,libcoap,v$(LIBCOAP_VERSION))
|
|
LIBCOAP_INSTALL_STAGING = YES
|
|
LIBCOAP_LICENSE = GPL-2.0+ or BSD-2-Clause
|
|
LIBCOAP_LICENSE_FILES = COPYING LICENSE.GPL LICENSE.BSD
|
|
LIBCOAP_DEPENDENCIES = host-pkgconf
|
|
LIBCOAP_CONF_OPTS = --disable-examples
|
|
LIBCOAP_AUTORECONF = YES
|
|
|
|
$(eval $(autotools-package))
|