RE: [poky] [PATCH] poky.conf: Set the distro name to "scarthgap"

> -----Original Message-----
> From: [email protected] <[email protected]> On Behalf
> Of Richard Purdie
> Sent: den 6 mars 2024 23:52
> To: Peter Kjellerstedt <[email protected]>; Bruce Ashfield
> <[email protected]>
> Cc: [email protected]
> Subject: Re: [poky] [PATCH] poky.conf: Set the distro name to "scarthgap"
> 
> On Wed, 2024-03-06 at 08:59 -0800, Peter Kjellerstedt wrote:
> > I am just following the established procedure for integrating changes
> > to OE: send a patch, wait for it to be accepted or receive feedback,
> > if nothing happens within a reasonable time frame (where I typically
> > wait about a week), then ping the patch as it may have been missed.
> >
> > Since I expect us to be using M3 to do our preparations for the
> > upcoming release, I thought it appropriate to give the patch a little
> > nudge since simple things like this are easily overlooked when
> > focusing on the more problematic integrations.
> >
> > And the reason I sent it as a patch rather than a request to go and
> > change the value is because I assume it is a faster/easier process to
> > take a prepared patch rather than to manually do the change (even if
> > it is just a one line change like this).
> >
> > > Richard obviously knows what has to be done to prepare for a
> > > release, and if it hasn't been done yet, there are likely reasons
> > > for that.
> 
> As Bruce suspects, I do have scripts that do a variety of these things
> for releases. They're not nice well written scripts and make
> assumptions about state. My local trees are in such a mess due to
> ongoing integration issues I don't dare run them atm and if I take the
> patches, I then have to resolve the conflicts with the scripts as well.
> Most of that is because I have code which I don't know whether we're
> going to end up merging or not and it has implications on the helper
> branches and autobuilder config.

Ok, I understand. 

> 
> Basically, the bottom line is there are many different problems, lots
> of people want my time and I just can't do everything. This one hasn't
> made it to a priority high enough to spend time on fixing :/.
> 
> Cheers,
> 
> Richard

I should be able to force an override for it in our Scarthgap-adaptation 
layer so we will manage even if this is not in place for M3.

//Peter