[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-architecture
Subject:    Re: [Openembedded-architecture] Template handling in OE-Core
From:       "Richard Purdie" <richard.purdie () linuxfoundation ! org>
Date:       2022-09-28 20:55:58
Message-ID: 938e6343c342569219312c12222b41b181db64e7.camel () linuxfoundation ! org
[Download RAW message or body]

On Wed, 2022-09-28 at 20:02 +0000, Peter Kjellerstedt wrote:
> > -----Original Message-----
> > From: Alexander Kanavin <alex.kanavin@gmail.com>
> > Sent: den 28 september 2022 16:41
> > To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> > Cc: Richard Purdie <richard.purdie@linuxfoundation.org>;
> > openembedded-
> > architecture <openembedded-architecture@lists.openembedded.org>
> > Subject: Re: Template handling in OE-Core
> > 
> > On Wed, 28 Sept 2022 at 16:25, Peter Kjellerstedt
> > <peter.kjellerstedt@axis.com> wrote:
> > 
> > > Personally, I would expect the file to contain the latest value
> > > used
> > > for TEMPLATECONF. I.e., if I remove the local.conf file to
> > > regenerate
> > > it because there has been upstream changes, I would expect it to
> > > use
> > > the TEMPLATECONF I specify at that time, and for that value to be
> > > recorded for posterity.
> > > 
> > > That said, I doubt the value of TEMPLATECONF will actually change
> > > for
> > > an existing build environment, so this is probably more on the
> > > theoretical side.
> > 
> > This would complicate the logic (update only if some config was
> > updated), and if you remove local.conf but not bblayers.conf, so
> > that
> > one is updated, but not the other, it is not anymore possible to
> > tell
> > what came from where. Creating it once at the start is more
> > straightforward, even if origins of further updates are not
> > recorded.
> > 
> > Alex
> 
> Yeah, I guess it's a case of damned if you do, damned if you don't. 
> However, as this patch solves our problem, I support applying this
> patch.

Ultimately, I think we'll end up removing this file. Whilst I
understand we might want to track where things came from, I think the
current way breaks for two files and doesn't give version information
anyway.

There may be a better way with a copy alongside of the template,
something involving symlinks or something else.

Meanwhile though I'll take this patch as it solves the problem enough
for release and as far as I can tell, shouldn't make anything worse.

Cheers,

Richard






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1655): \
https://lists.openembedded.org/g/openembedded-architecture/message/1655 Mute This \
Topic: https://lists.openembedded.org/mt/93968540/4454510 Group Owner: \
                openembedded-architecture+owner@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub \
                [openembedded-architecture@marc.info]
-=-=-=-=-=-=-=-=-=-=-=-



[prev in list] [next in list] [prev in thread] [next in thread]