From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/3] opkg: Regenerate config after input variable changes
Date: Fri, 20 Mar 2020 12:31:05 +0100 [thread overview]
Message-ID: <20200320113105.GA7533@pengutronix.de> (raw)
In-Reply-To: <20200227144449.29660-2-ada@thorsis.com>
On Thu, Feb 27, 2020 at 03:44:47PM +0100, Alexander Dahl wrote:
> Some values in `/etc/opkg/opkg.conf` are replaced by 'install_replace'
> in targetinstall stage. Especially PTXCONF_OPKG_OPKG_CONF_URL can
> contain other variables which might change frequently when developing.
Right, this is a problem for other packages as well. The more general fix
ist to hash the evaluated PTXCONF_* variables instead. I've implemented
this here. It should hit master once all my test have passed. But maybe
only for the April release.
Michael
> The default for example contains PTXCONF_PROJECT_VERSION which changes
> with every git commit. The place where opkg packages are put to on the
> dev host would differ then from the opkg.conf on the target. Trigger a
> rebuild of the targetinstall stage keeps that in sync.
>
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> ---
> rules/opkg.make | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/rules/opkg.make b/rules/opkg.make
> index 23390ce0f..2396853fe 100644
> --- a/rules/opkg.make
> +++ b/rules/opkg.make
> @@ -53,6 +53,17 @@ OPKG_CONF_OPT := \
> # Target-Install
> # ----------------------------------------------------------------------------
>
> +ifdef PTXCONF_OPKG_OPKG_CONF
> +OPKG_STAMP := $(call remove_quotes, \
> + $(PTXCONF_OPKG_OPKG_CONF_URL) \
> + $(PTXDIST_IPKG_ARCH_STRING) \
> + $(PTXCONF_OPKG_OPKG_CONF_CHECKSIG))
> +
> +ifneq ($(strip $(OPKG_STAMP)),$(strip $(call ptx/force-sh cat $(STATEDIR)/opkg.stamp 2>/dev/null)))
> +PHONY += $(STATEDIR)/opkg.targetinstall
> +endif
> +endif
> +
> $(STATEDIR)/opkg.targetinstall:
> @$(call targetinfo)
>
> @@ -104,6 +115,9 @@ endif
>
> @$(call install_finish, opkg)
>
> +ifdef PTXCONF_OPKG_OPKG_CONF
> + @echo "$(OPKG_STAMP)" > $(STATEDIR)/opkg.stamp
> +endif
> @$(call touch)
>
> # vim: syntax=make
> --
> 2.20.1
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-03-20 11:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 14:44 [ptxdist] [PATCH 0/3] Minor build improvements Alexander Dahl
2020-02-27 14:44 ` [ptxdist] [PATCH 1/3] opkg: Regenerate config after input variable changes Alexander Dahl
2020-03-20 11:31 ` Michael Olbrich [this message]
2020-03-27 13:24 ` Michael Olbrich
2020-02-27 14:44 ` [ptxdist] [PATCH 2/3] os-release: Make date string reproducible Alexander Dahl
2020-02-28 10:16 ` Roland Hieber
2020-02-28 15:40 ` Roland Hieber
2020-02-28 16:14 ` Alexander Dahl
2020-02-29 8:48 ` Michael Olbrich
2020-02-29 17:41 ` Alexander Dahl
2020-03-20 11:38 ` Michael Olbrich
2020-02-27 14:44 ` [ptxdist] [PATCH 3/3] rootfs: issue: " Alexander Dahl
2020-03-20 11:39 ` Michael Olbrich
2020-03-20 12:08 ` Alexander Dahl
2020-03-20 12:44 ` 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=20200320113105.GA7533@pengutronix.de \
--to=m.olbrich@pengutronix.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