Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: "Flávio Tapajós" <flavio.tapajos@newtesc.com.br>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/rsyslog: add libdbi-drivers optional dependency
Date: Tue, 28 Nov 2023 16:07:59 +0200	[thread overview]
Message-ID: <87edgax937.fsf@tarshish> (raw)
In-Reply-To: <20231128134301.6018-2-flavio.tapajos@newtesc.com.br>

Hi Flávio,

On Tue, Nov 28 2023, Flávio Tapajós wrote:
> Needed in order to use omlibdbi module
>
> Signed-off-by: Flávio Tapajós <flavio.tapajos@newtesc.com.br>
> ---
>  package/rsyslog/Config.in  | 1 +
>  package/rsyslog/rsyslog.mk | 7 +++++++
>  2 files changed, 8 insertions(+)
>
> diff --git a/package/rsyslog/Config.in b/package/rsyslog/Config.in
> index 3ba326191a..e07db818e2 100644
> --- a/package/rsyslog/Config.in
> +++ b/package/rsyslog/Config.in
> @@ -13,6 +13,7 @@ config BR2_PACKAGE_RSYSLOG
>  	select BR2_PACKAGE_LIBESTR
>  	select BR2_PACKAGE_LIBLOGGING
>  	select BR2_PACKAGE_LIBFASTJSON
> +	select BR2_PACKAGE_LIBDBI_DRIVERS

The code below indicates that BR2_PACKAGE_LIBDBI_DRIVERS is an optional
dependency. No need to force 'select' in that case. The user can enable
BR2_PACKAGE_LIBDBI_DRIVERS for the omlibdbi functionality.

baruch

>  	help
>  	  Rsyslog is a powerful and flexible syslog implementation
>  
> diff --git a/package/rsyslog/rsyslog.mk b/package/rsyslog/rsyslog.mk
> index cf9f2c0e79..8ea92ea785 100644
> --- a/package/rsyslog/rsyslog.mk
> +++ b/package/rsyslog/rsyslog.mk
> @@ -151,6 +151,13 @@ RSYSLOG_CONF_OPTS += \
>  	--disable-omjournal
>  endif
>  
> +ifeq ($(BR2_PACKAGE_LIBDBI_DRIVERS),y)
> +RSYSLOG_CONF_OPTS += --enable-libdbi
> +RSYSLOG_DEPENDENCIES += libdbi-drivers
> +else
> +RSYSLOG_CONF_OPTS += --disable-libdbi
> +endif
> +
>  define RSYSLOG_INSTALL_INIT_SYSTEMD
>  	$(INSTALL) -m 0644 -D package/rsyslog/rsyslog.service \
>  		$(TARGET_DIR)/usr/lib/systemd/system/rsyslog.service


-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-11-28 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 13:43 [Buildroot] [PATCH 1/2] package/rsyslog: bump version to 8.2310.0 Flávio Tapajós
2023-11-28 13:43 ` [Buildroot] [PATCH 2/2] package/rsyslog: add libdbi-drivers optional dependency Flávio Tapajós
2023-11-28 14:07   ` Baruch Siach via buildroot [this message]
2023-11-28 14:07 ` [Buildroot] [PATCH 1/2] package/rsyslog: bump version to 8.2310.0 Baruch Siach via buildroot
  -- strict thread matches above, loose matches on Subject: below --
2023-11-29 11:02 Flávio Tapajós
2023-11-29 11:02 ` [Buildroot] [PATCH 2/2] package/rsyslog: add libdbi-drivers optional dependency Flávio Tapajós
2023-12-02  8:39   ` Peter Korsgaard

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=87edgax937.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=flavio.tapajos@newtesc.com.br \
    /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