From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/luasyslog: bump to version 2.2.0 (fork)
Date: Thu, 7 Jan 2021 23:20:31 +0100 [thread overview]
Message-ID: <20210107232031.2ac9e312@windsurf.home> (raw)
In-Reply-To: <20200422092253.25466-1-francois.perrad@gadz.org>
Hello Fran?ois,
On Wed, 22 Apr 2020 11:22:53 +0200
Francois Perrad <fperrad@gmail.com> wrote:
> this fork has a good support for Lua 5.3the initial 1.0.0 is available as rock (which contains a tarball)
> https://luarocks.org/modules/luarocks/luasyslog
> but there is no public repository.
>
> the fork has a public repository
> https://github.com/ntd/luasyslog/
> it is available as rock
> https://luarocks.org/modules/ntd/luasyslog
> unfortunately the rockspec uses a build method unavaible in our BR luarocks infrastructure
> so, the autotools infrastructure must replace the luarocks one.
>
> this fork has a good support for Lua 5.3
> so, the patch "compat Lua 5.3" becomes useless.
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
I've applied after reworking the commit log quite a bit. Also, some
other changes, see below.
> -LUASYSLOG_VERSION = 1.0.0-2
> +LUASYSLOG_VERSION = 2.2.0
> +LUASYSLOG_SITE = $(call github,ntd,luasyslog,$(LUASYSLOG_VERSION))
> +LUASUSLOG_DEPENDENCIES = luainterpreter
Typo: LUASUSLOG_DEPENDENCIES should have been LUASYSLOG_DEPENDENCIES.
This was caught by "make check-package", so you could have seen it.
> LUASYSLOG_LICENSE = MIT
> -LUASYSLOG_LICENSE_FILES = $(LUASYSLOG_SUBDIR)/COPYING
> +LUASYSLOG_LICENSE_FILES = COPYING
> +LUASYSLOG_AUTORECONF = YES
I've added a comment that says why autoreconf is needed.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-07 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 9:22 [Buildroot] [PATCH] package/luasyslog: bump to version 2.2.0 (fork) Francois Perrad
2021-01-07 22:20 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-30 18:24 Francois Perrad
2019-07-01 20:30 ` Arnout Vandecappelle
2019-07-02 18:51 ` François Perrad
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=20210107232031.2ac9e312@windsurf.home \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox