mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Enrico Jörns" <ejo@pengutronix.de>
To: Alexander Dahl <post@lespocky.de>
Cc: Alexander Dahl <ada@thorsis.com>, ejo <ejo@pengutronix.de>,
	ptxdist@pengutronix.de, jlu@pengutronix.de
Subject: Re: [ptxdist] [PATCH 3/5] RAUC: leverage --disable-create option to shrink size for target RAUC
Date: Thu, 16 Jun 2022 15:53:04 +0200	[thread overview]
Message-ID: <0268a579efc130bbf5040ca145b2911c61ef6e39.camel@pengutronix.de> (raw)
In-Reply-To: <20220616061632.GC2412@falbala.internal.home.lespocky.de>

Hello Alex,

Am Donnerstag, dem 16.06.2022 um 08:16 +0200 schrieb Alexander Dahl:
> > > > 
> > > > diff --git a/rules/host-rauc.make b/rules/host-rauc.make
> > > > index c78a518f6..1851aee9a 100644
> > > > --- a/rules/host-rauc.make
> > > > +++ b/rules/host-rauc.make
> > > > @@ -23,6 +23,7 @@ HOST_RAUC_CONF_OPT	:= \
> > > >  	$(HOST_AUTOCONF) \
> > > >  	--disable-code-coverage \
> > > >  	--disable-valgrind \
> > > > +	--enable-create \
> > > 
> > > From the cover letter I understood this is a new post 1.5 option,
> > > right?
> > 
> > almost, as the cover-letter explicitly notes this is a post 1.3 option. ;)
> > 
> > And this line is only for completeness. The added option in RAUC is semantically
> > --disable-create and --enable-create is the default.
> 
> make rules in ptxdist pin down _all_ configure options, so if that was
> missing for 1.5 package it was already forgotten to set when upgrading
> from 1.3 or 1.4.

yes, there have been no adaptions since the initial recipe submission.

Seems as if I've won an extra price for this round. \o/

> > > >  	--disable-service \
> > > >  	--disable-network \
> > > >  	--disable-json
> > > > diff --git a/rules/rauc.in b/rules/rauc.in
> > > > index 832967b44..e43692846 100644
> > > > --- a/rules/rauc.in
> > > > +++ b/rules/rauc.in
> > > > @@ -27,6 +27,16 @@ menuconfig RAUC
> > > >  
> > > >  if RAUC
> > > >  
> > > > +config RAUC_CREATE
> > > > +	bool
> > > > +	prompt "Enable bundle creation support on target"
> > > > +	default n
> > > > +	help
> > > > +	  Enables support for creating bundles on target.
> > > > +	  Disabling this will remove functionality required for bundle
> > > > +	  creation which is not required on the target in most cases and thus
> > > > +	  allows to save space.
> > > > +
> > > >  config RAUC_SERVICE
> > > >  	bool
> > > >  	prompt "Enable service (D-Bus) support"
> > > > diff --git a/rules/rauc.make b/rules/rauc.make
> > > > index 820583e59..e001956a5 100644
> > > > --- a/rules/rauc.make
> > > > +++ b/rules/rauc.make
> > > > @@ -41,6 +41,7 @@ RAUC_CONF_OPT	:= \
> > > >  	$(GLOBAL_LARGE_FILE_OPTION) \
> > > >  	--disable-code-coverage \
> > > >  	--disable-valgrind \
> > > > +	--$(call ptx/endis,PTXCONF_RAUC_CREATE)-create \
> > > 
> > > Same here. This should have set explicitly to a sensible default with
> > > the package update. Making this optional would just change that line
> > > then instead of adding it.
> > 
> > See above. The ptxdist default for RAUC_CREATE ("n") leads to --disable-create
> > which changes the RAUC default (which is --enable-create).
> 
> I understand RAUC has some opinion what should be default. Some
> embedded build systems like buildroot stick with those defaults (for
> all options not explicitly set through menu). Others like ptxdist set
> all configure options. The script 'scripts/configure_helper.py' helps
> determining missing options not set. See example output for package
> host-rauc on a ptxdist 2021.06.0 based BSP:

Since I know some of them, I'd tend to say the group of 'Others' exclusively
consists of ptxdist to the best of my knowledge.
But yes, in theory I am aware of this design decision ;)

Thanks for the helper script, I'll give it a try.

> 	% ~/src/ptxdist/scripts/configure_helper.py -p host-rauc
> 	--- rules/host-rauc.make
> 	+++ rauc-1.5.1
> 	@@ -1,6 +1,17 @@
> 			--prefix=
> 	+       --enable-debug=yes/info/profile/no
> 	+       --disable-largefile
> 	+       --enable-compile-warnings=no/yes/error
> 	+       --disable-Werror
> 			--disable-code-coverage
> 			--disable-valgrind
> 			--disable-service
> 	+       --disable-create
> 			--disable-network
> 			--disable-json
> 	+       --enable-gpt
> 	+       --with-gcov=GCOV
> 	+       --with-systemdunitdir=DIR
> 	+       --with-dbuspolicydir=DIR
> 	+       --with-dbussystemservicedir=DIR
> 	+       --with-dbusinterfacesdir=DIR
> 
> You see --disable-create is not the only option not set in
> rules/host-rauc.make and I guess it might look similar for rauc.make?

It does, yes (with a little bit less diff lines).

> Pinning down the old options should go to a patch before bumping the
> version.

Give me a second..


Best regards

Enrico

> 
> Greets
> Alex
> 
> > 
> > Regards, Enrico
> > 
> > > Greets
> > > Alex
> > > 
> > > >  	--$(call ptx/endis,PTXCONF_RAUC_SERVICE)-service \
> > > >  	--$(call ptx/endis,PTXCONF_RAUC_NETWORK)-network \
> > > >  	--$(call ptx/endis,PTXCONF_RAUC_STREAMING)-streaming \
> > > > -- 
> > > > 2.30.2
> > > > 
> > > > 
> > > 
> > > 
> > 
> > -- 
> > Pengutronix e.K.                           | Enrico Jörns                |
> > Embedded Linux Consulting & Support        | https://www.pengutronix.de/ |
> > Steuerwalder Str. 21                       | Phone: +49-5121-206917-180  |
> > 31137 Hildesheim, Germany                  | Fax:   +49-5121-206917-9    |
> 

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Embedded Linux Consulting & Support        | https://www.pengutronix.de/ |
Steuerwalder Str. 21                       | Phone: +49-5121-206917-180  |
31137 Hildesheim, Germany                  | Fax:   +49-5121-206917-9    |



  reply	other threads:[~2022-06-16 13:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 14:22 [ptxdist] [PATCH 0/5] RAUC: update to v1.7 and add some new options Enrico Jorns
2022-06-15 14:22 ` [ptxdist] [PATCH 1/5] RAUC: version bump 1.5.1 -> 1.7 Enrico Jorns
2022-06-20  6:19   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-06-15 14:22 ` [ptxdist] [PATCH 2/5] RAUC: add option to enable streaming support Enrico Jorns
2022-06-17  6:28   ` Michael Olbrich
2022-06-17  9:47     ` Enrico Jörns
2022-06-17 10:27       ` Michael Olbrich
2022-06-17 10:48         ` Michael Olbrich
2022-06-17 11:47           ` Enrico Jörns
2022-06-17 12:04             ` Michael Olbrich
2022-06-17 10:57         ` Alexander Dahl
2022-06-20  6:19   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-06-15 14:22 ` [ptxdist] [PATCH 3/5] RAUC: leverage --disable-create option to shrink size for target RAUC Enrico Jorns
2022-06-15 15:48   ` Alexander Dahl
2022-06-15 21:03     ` Enrico Jörns
2022-06-16  6:16       ` Alexander Dahl
2022-06-16 13:53         ` Enrico Jörns [this message]
2022-06-20  6:19   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-06-15 14:22 ` [ptxdist] [PATCH 4/5] image-rauc: add support for crypt bundles Enrico Jorns
2022-06-20  6:20   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-06-15 14:22 ` [ptxdist] [PATCH 5/5] image-rauc: default to 'verity' bundle format Enrico Jorns
2022-06-20  6:20   ` [ptxdist] [APPLIED] " Michael Olbrich

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=0268a579efc130bbf5040ca145b2911c61ef6e39.camel@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=ada@thorsis.com \
    --cc=jlu@pengutronix.de \
    --cc=post@lespocky.de \
    --cc=ptxdist@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