2013-06-06 01:53:30 +02:00
|
|
|
################################################################################
|
2012-05-28 15:36:48 +02:00
|
|
|
#
|
|
|
|
# xinetd
|
|
|
|
#
|
2013-06-06 01:53:30 +02:00
|
|
|
################################################################################
|
2013-06-06 01:53:25 +02:00
|
|
|
|
package: remove non-conventional prefix/suffix from github-fetched packages
On Github, a large number of projects name their tag
<some-prefix>-0.3-<some-suffix> (i.e release-3.0, poco-0.1-release,
etc.). In fact majority of the cased adressed in this commit concerns
prefixes.
In most packages, we encode those prefix/suffix in the <pkg>_VERSION
variable.
The problem with this approach 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/suffix" and
using that they drop the prefix/suffix to really get the version. For
example on https://release-monitoring.org/project/5418/ the latest
release of "poco" is "1.8.1", not "poco-1.8.1-release".
Therefore, a number of packages in Buildroot have a version that
doesn't match with release-monitoring.org.
Since really the version number of 1.8.1, is makes sense to update our
packages to drop these prefixes/suffixes.
This commit addreses the case of github-fetched packages with
non-conventional prefixes/suffixes.
Note that these changes modify the name of the files stored in DL_DIR,
which means that this will force a re-download of those package source
code for all users, and requires a change to their .hash file.
Signed-off-by: Victor Huesca <victor.huesca@bootlin.com>
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-06-12 08:42:08 +02:00
|
|
|
XINETD_VERSION = 2-3-15
|
|
|
|
XINETD_SITE = $(call github,xinetd-org,xinetd,xinetd-$(XINETD_VERSION))
|
.mk files: bulk aligment and whitespace cleanup of assignments
The Buildroot coding style defines one space around make assignments and
does not align the assignment symbols.
This patch does a bulk fix of offending packages. The package
infrastructures (or more in general assignments to calculated variable
names, like $(2)_FOO) are not touched.
Alignment of line continuation characters (\) is kept as-is.
The sed command used to do this replacement is:
find * -name "*.mk" | xargs sed -i \
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*$#\1 \2#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\]\+\)$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\ \t]\+\s*\\\)\s*$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\(\s*\\\)#\1 \2\3#'
Brief explanation of this command:
^\([A-Z0-9a-z_]\+\) a regular variable at the beginning of the line
\([?:+]\?=\) any assignment character =, :=, ?=, +=
\([^\\]\+\) any string not containing a line continuation
\([^\\ \t]\+\s*\\\) string, optional whitespace, followed by a
line continuation character
\(\s*\\\) optional whitespace, followed by a line
continuation character
Hence, the first subexpression handles empty assignments, the second
handles regular assignments, the third handles regular assignments with
line continuation, and the fourth empty assignments with line
continuation.
This expression was tested on following test text: (initial tab not
included)
FOO = spaces before
FOO = spaces before and after
FOO = tab before
FOO = tab and spaces before
FOO = tab after
FOO = tab and spaces after
FOO = spaces and tab after
FOO = \
FOO = bar \
FOO = bar space \
FOO = \
GENIMAGE_DEPENDENCIES = host-pkgconf libconfuse
FOO += spaces before
FOO ?= spaces before and after
FOO :=
FOO =
FOO =
FOO =
FOO =
$(MAKE1) CROSS_COMPILE=$(TARGET_CROSS) -C
AT91BOOTSTRAP3_DEFCONFIG = \
AXEL_DISABLE_I18N=--i18n=0
After this bulk change, following manual fixups were done:
- fix line continuation alignment in cegui06 and spice (the sed
expression leaves the number of whitespace between the value and line
continuation character intact, but the whitespace before that could have
changed, causing misalignment.
- qt5base was reverted, as this package uses extensive alignment which
actually makes the code more readable.
Finally, the end result was manually reviewed.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Cc: Yann E. Morin <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-10-07 09:06:03 +02:00
|
|
|
XINETD_LICENSE = xinetd license
|
2012-08-04 04:57:46 +02:00
|
|
|
XINETD_LICENSE_FILES = COPYRIGHT
|
2012-05-28 15:36:48 +02:00
|
|
|
|
2012-11-04 08:34:18 +01:00
|
|
|
XINETD_CFLAGS = $(TARGET_CFLAGS)
|
|
|
|
|
|
|
|
# Three cases here:
|
|
|
|
# 1. We have libtirpc, use it by passing special flags
|
|
|
|
# 2. We have native RPC support, use it, no need to pass special
|
|
|
|
# flags (so this case 2 is implicit and not visible below)
|
|
|
|
# 3. We don't have RPC support, pass -DNO_RPC to disable it
|
|
|
|
ifeq ($(BR2_PACKAGE_LIBTIRPC),y)
|
2015-07-26 20:45:17 +02:00
|
|
|
XINETD_DEPENDENCIES += libtirpc host-pkgconf
|
|
|
|
XINETD_CFLAGS += "`$(PKG_CONFIG_HOST_BINARY) --cflags libtirpc`"
|
|
|
|
XINETD_LIBS += "`$(PKG_CONFIG_HOST_BINARY) --libs libtirpc`"
|
2012-11-04 08:34:18 +01:00
|
|
|
else ifeq ($(BR2_TOOLCHAIN_HAS_NATIVE_RPC),)
|
|
|
|
XINETD_CFLAGS += -DNO_RPC
|
2012-06-16 22:58:26 +02:00
|
|
|
endif
|
|
|
|
|
2012-11-04 08:34:18 +01:00
|
|
|
XINETD_CONF_ENV += \
|
|
|
|
CFLAGS="$(XINETD_CFLAGS)" \
|
|
|
|
LIBS="$(XINETD_LIBS)"
|
|
|
|
|
2014-09-27 21:32:38 +02:00
|
|
|
XINETD_MAKE_OPTS = AR="$(TARGET_AR)"
|
2012-06-18 17:18:32 +02:00
|
|
|
|
2012-07-03 00:07:32 +02:00
|
|
|
$(eval $(autotools-package))
|