Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "J. Neuschäfer via buildroot" <buildroot@buildroot.org>
Cc: "J. Neuschäfer" <j.neuschaefer@gmx.net>
Subject: Re: [Buildroot] [PATCH 8/8] tipidee: new package
Date: Mon, 8 Jul 2024 23:24:40 +0200	[thread overview]
Message-ID: <20240708232440.56e59da4@windsurf> (raw)
In-Reply-To: <20240704-tipidee-v1-8-5ef0942b2025@gmx.net>

Hello,

On Thu, 04 Jul 2024 21:40:34 +0200
J. Neuschäfer via buildroot <buildroot@buildroot.org> wrote:

> Signed-off-by: J. Neuschäfer <j.neuschaefer@gmx.net>

Thanks for this contribution!

> +if BR2_PACKAGE_TIPIDEE
> +
> +config BR2_PACKAGE_TIPIDEE_CONFIGURATION
> +	bool "install a configuration file to /etc/tipidee.conf.cdb"
> +	select BR2_PACKAGE_HOST_TIPIDEE
> +	help
> +	  Build a tipidee configuration and install it to the target.
> +
> +config BR2_PACKAGE_TIPIDEE_CONFIGURATION_FILE
> +	string "configuration source file"
> +	default "$(CONFIG_DIR)/tipidee.conf"
> +	depends on BR2_PACKAGE_TIPIDEE_CONFIGURATION
> +	help
> +	  The configuration file in source (text) format, documented at:
> +
> +	  https://skarnet.org/software/tipidee/tipidee.conf.html

I'm not sure those configuration options are really needed. We usually
don't make the configuration file configurable, and leave that up to a
rootfs-overlay. I understand that the configuration is apparently
"compiled", but I would perhaps leave that up to be overridden by a
post-build script? Or perhaps we should do this configuration file
"compilation" as a TARGET_FINALIZE_HOOKS so that it happens after
rootfs-overlay are copied, allowing the user to override the
configuration file, while still seeing it "compiled"?

> diff --git a/package/tipidee/Config.in.host b/package/tipidee/Config.in.host
> new file mode 100644
> index 0000000000..93e548df1e
> --- /dev/null
> +++ b/package/tipidee/Config.in.host
> @@ -0,0 +1,8 @@
> +config BR2_HOST_PACKAGE_TIPIDEE
> +	bool "host tipidee"
> +	depends on BR2_USE_MMU # skalibs
> +	select BR2_PACKAGE_SKALIBS
> +	help
> +	  This package builds the tipidee-config tool for the host.
> +
> +	  https://skarnet.org/software/tipidee/

I'm not sure we really need a visible config option for this,
host-tipidee is going to be a dependency of tipidee anyway.

> diff --git a/package/tipidee/tipidee.mk b/package/tipidee/tipidee.mk
> new file mode 100644
> index 0000000000..2fde75b87d
> --- /dev/null
> +++ b/package/tipidee/tipidee.mk
> @@ -0,0 +1,72 @@
> +################################################################################
> +#
> +# tipidee
> +#
> +################################################################################
> +
> +TIPIDEE_VERSION = 0.0.5.0
> +TIPIDEE_SITE = https://skarnet.org/software/tipidee
> +TIPIDEE_LICENSE = ISC
> +TIPIDEE_LICENSE_FILES = COPYING
> +TIPIDEE_INSTALL_STAGING = YES
> +TIPIDEE_DEPENDENCIES = skalibs
> +
> +TIPIDEE_CONF_OPTS = \
> +	--prefix=/ \

This looks odd, why not --prefix=/usr ?

The rest really looks super reasonable to me, good work!

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-07-08 21:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 19:40 [Buildroot] [PATCH 0/8] Various skarnet.org updates and new tipidee package J. Neuschäfer via buildroot
2024-07-04 19:40 ` [Buildroot] [PATCH 1/8] skalibs: bump to version 2.14.2.0 J. Neuschäfer via buildroot
2024-07-04 19:40 ` [Buildroot] [PATCH 2/8] s6: bump to version 2.13.0.1 J. Neuschäfer via buildroot
2024-07-04 19:40 ` [Buildroot] [PATCH 3/8] execline: bump to version 2.9.6.0 J. Neuschäfer via buildroot
2024-07-04 19:40 ` [Buildroot] [PATCH 4/8] s6-networking: bump to version 2.7.0.3 J. Neuschäfer via buildroot
2024-07-04 19:40 ` [Buildroot] [PATCH 5/8] s6-rc: bump to version 0.5.4.3 J. Neuschäfer via buildroot
2024-07-04 19:40 ` [Buildroot] [PATCH 6/8] mdevd: bump to version 0.1.6.4 J. Neuschäfer via buildroot
2024-07-04 19:40 ` [Buildroot] [PATCH 7/8] s6-dns: bump to version 2.3.7.2 J. Neuschäfer via buildroot
2024-07-04 19:40 ` [Buildroot] [PATCH 8/8] tipidee: new package J. Neuschäfer via buildroot
2024-07-08 21:24   ` Thomas Petazzoni via buildroot [this message]
2024-07-09 19:30     ` J. Neuschäfer via buildroot
2024-07-04 19:44 ` [Buildroot] [PATCH 0/8] Various skarnet.org updates and new tipidee package J. Neuschäfer via buildroot
2024-07-08 21:13 ` Thomas Petazzoni via buildroot
2024-07-08 22:45   ` J. Neuschäfer via buildroot

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=20240708232440.56e59da4@windsurf \
    --to=buildroot@buildroot.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox