From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Joachim Wiberg <troglobit@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] package/watchdogd: bump to version 4.0
Date: Mon, 5 Feb 2024 23:22:15 +0100 [thread overview]
Message-ID: <ZcFfl7qCM9_NYuHJ@landeda> (raw)
In-Reply-To: <20240130215628.884512-2-troglobit@gmail.com>
Joachim, All,
On 2024-01-30 22:56 +0100, Joachim Wiberg spake thusly:
> For details, see https://github.com/troglobit/watchdogd/releases/tag/4.0
>
> - Major feature upgrade, command line and .conf files compatible
> - LICENSE hash update due to update in copyright years
> - Enabling system monitor plugins have changed syntax upstream. The
> `--with-foo=SECONDS` is now just `--with-foo`
>
> This last upstream change require converting affected Config.in options
> from int -> bool. Legacy _WRAP:ers have been added to Config.legacy.in,
> modeled on BR2_TARGET_ROOTFS_EXT2_BLOCKS.
>
> Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
> ---
[--SNIP--]
> diff --git a/package/watchdogd/watchdogd.mk b/package/watchdogd/watchdogd.mk
> index ea033b4e71..2e67c2847e 100644
> --- a/package/watchdogd/watchdogd.mk
> +++ b/package/watchdogd/watchdogd.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -WATCHDOGD_VERSION = 3.5
> +WATCHDOGD_VERSION = 4.0
> WATCHDOGD_SITE = https://github.com/troglobit/watchdogd/releases/download/$(WATCHDOGD_VERSION)
> WATCHDOGD_LICENSE = ISC
> WATCHDOGD_LICENSE_FILES = LICENSE
> @@ -20,28 +20,29 @@ else
> WATCHDOGD_CONF_OPTS += --enable-builtin-tests
> endif
I also added explicit --without-XXX options for the new monitors, by the
way.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-05 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 7:41 [Buildroot] [PATCH 0/3] package/watchdogd: version bump and major Config.in rewrite Joachim Wiberg
2024-01-15 7:41 ` [Buildroot] [PATCH 1/3] package/watchdogd: bump to version 4.0 Joachim Wiberg
2024-01-15 7:41 ` [Buildroot] [PATCH 2/3] package/watchdogd: convert Config.in options, int -> bool Joachim Wiberg
2024-01-27 17:18 ` Yann E. MORIN
2024-01-28 8:54 ` troglobit
2024-01-30 21:56 ` [Buildroot] [PATCH v2 0/2] package/watchdogd: slightly messy bump to v4.0 Joachim Wiberg
2024-01-30 21:56 ` [Buildroot] [PATCH v2 1/2] package/watchdogd: bump to version 4.0 Joachim Wiberg
2024-02-05 22:20 ` Yann E. MORIN
2024-02-05 22:22 ` Yann E. MORIN [this message]
2024-01-30 21:56 ` [Buildroot] [PATCH v2 2/2] package/watchdogd: add menuconfig support for new system monitors Joachim Wiberg
2024-02-05 22:23 ` Yann E. MORIN
2024-01-15 7:41 ` [Buildroot] [PATCH 3/3] " Joachim Wiberg
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=ZcFfl7qCM9_NYuHJ@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=troglobit@gmail.com \
/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.