DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: Roland Hieber <rhi@pengutronix.de>
Cc: Alexander Dahl <ada@thorsis.com>,
	Michael Olbrich <m.olbrich@pengutronix.de>,
	distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH v3 4/4] ptxconfig: create menu for DistroKit-specific rules
Date: Thu, 20 Jun 2024 12:28:06 +0200	[thread overview]
Message-ID: <20240620-harness-pastel-bcdf8f936b80@thorsis.com> (raw)
In-Reply-To: <20240619123237.1396057-5-rhi@pengutronix.de>

Hello Roland,

Am Wed, Jun 19, 2024 at 02:32:37PM +0200 schrieb Roland Hieber:
> This way the main menu doesn't get cluttered up with random recipes.
> 
> Link: https://lore.distrokit.org/distrokit/20240613-whenever-enduring-698a9b93370b@thorsis.com/
> Suggested-by: Alexander Dahl <ada@thorsis.com>
> Reviewed-by: Michael Olbrich <m.olbrich@pengutronix.de>
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
>  configs/ptxconfig      | 5 +++++
>  rules/distrokit.in     | 5 +++++
>  rules/rauc-udev.in     | 2 +-
>  rules/repart-config.in | 2 +-
>  4 files changed, 12 insertions(+), 2 deletions(-)
>  create mode 100644 rules/distrokit.in
> 
> diff --git a/configs/ptxconfig b/configs/ptxconfig
> index c7cdb62e16a5..fda7d198e6de 100644
> --- a/configs/ptxconfig
> +++ b/configs/ptxconfig
> @@ -2,8 +2,13 @@
>  # Automatically generated file; DO NOT EDIT.
>  # PTXdist 2024.05.0
>  #
> +
> +#
> +# DistroKit                     
> +#
>  PTXCONF_RAUC_UDEV=y
>  PTXCONF_REPART_CONFIG=y
> +# end of DistroKit                     
>  
>  #
>  # ------------------------------------
> diff --git a/rules/distrokit.in b/rules/distrokit.in
> new file mode 100644
> index 000000000000..559a5bde0ecd
> --- /dev/null
> +++ b/rules/distrokit.in
> @@ -0,0 +1,5 @@
> +## SECTION=project_specific
> +
> +menu "DistroKit                     "
> +source "generated/distrokit.in"
> +endmenu
> diff --git a/rules/rauc-udev.in b/rules/rauc-udev.in
> index f960c537f58f..d18f1c3197d5 100644
> --- a/rules/rauc-udev.in
> +++ b/rules/rauc-udev.in
> @@ -1,4 +1,4 @@
> -## SECTION=project_specific
> +## SECTION=distrokit
>  
>  config RAUC_UDEV
>  	tristate
> diff --git a/rules/repart-config.in b/rules/repart-config.in
> index db9828f669f2..ea803c015978 100644
> --- a/rules/repart-config.in
> +++ b/rules/repart-config.in
> @@ -1,4 +1,4 @@
> -## SECTION=project_specific
> +## SECTION=distrokit
>  
>  config REPART_CONFIG
>  	tristate "repart-config"

Looks good overall, so …

Reviewed-by: Alexander Dahl <ada@thorsis.com>

Greets
Alex




  reply	other threads:[~2024-06-20 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 12:32 [DistroKit] [PATCH v3 0/4] recipe cleanup Roland Hieber
2024-06-19 12:32 ` [DistroKit] [PATCH v3 1/4] datapartition: make it selectable Roland Hieber
2024-06-19 12:32 ` [DistroKit] [PATCH v3 2/4] datapartition: rename to repart-config Roland Hieber
2024-06-19 12:32 ` [DistroKit] [PATCH v3 3/4] binary_inst: remove outdated example Roland Hieber
2024-06-19 12:32 ` [DistroKit] [PATCH v3 4/4] ptxconfig: create menu for DistroKit-specific rules Roland Hieber
2024-06-20 10:28   ` Alexander Dahl [this message]
2024-06-20 10:48 ` [DistroKit] [PATCH v3 0/4] recipe cleanup Robert Schwebel

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=20240620-harness-pastel-bcdf8f936b80@thorsis.com \
    --to=ada@thorsis.com \
    --cc=distrokit@pengutronix.de \
    --cc=m.olbrich@pengutronix.de \
    --cc=rhi@pengutronix.de \
    /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