All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH 2/2] oe-setup-builddir: Do not hardcode invalid paths for templates
Date: Tue, 27 Sep 2022 16:06:35 +0000	[thread overview]
Message-ID: <faab0d74b95849bdb1d39ac0146dd523@axis.com> (raw)
In-Reply-To: <CANNYZj_rRJFsnOcSrkONYfmkZdUe1eCZKYcvnkpPj7jm7eVu+g@mail.gmail.com>

> -----Original Message-----
> From: Alexander Kanavin <alex.kanavin@gmail.com>
> Sent: den 27 september 2022 17:42
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>; OE-core
> <openembedded-core@lists.openembedded.org>
> Subject: Re: [OE-core] [PATCH 2/2] oe-setup-builddir: Do not hardcode
> invalid paths for templates
> 
> Now it's my time to rant at you, Peter. Brace yourself.
> 
> Let me just say this, you don't get to have expectations and
> entitlements, if none of your '500 developers' are working fulltime to
> help the core. I think you've been in the room last week when Nico and
> Philip presented the numbers and the downward trend of who is doing
> the work in core; what are you doing to address that situation, given
> the resources your organization has?

I (and the small team I am part of) is the proxy between them and Yocto. 
Thus I try to address their needs by making sure new versions of Yocto 
continues to work for them without having 500+ developers facing the 
same problems. I.e., it is my job to work with upstream, which is what 
I am trying to do here.

> We have a small handful of exhausted maintainers, I in particular have
> to squeeze my maintenance work between fixing various customer BSPs,
> and so it is on you to help us first.

Which is exactly what I am trying to do. I am trying to make sure that 
what has worked, continues to work, when it is not in opposition to the 
actual changes that you are making. You made this exact change (that 
my patch addresses) for OE and Poky because you realized that there was 
an error that could be avoided in a simple way. And I just want to 
extend that to be possible to do for all distributions besides Poky. 
This is typically something that affect those of us who have existing 
distributions and not users of the new way to setup the environment. 

> Otherwise, yes, I will say this:
> fix your scripts, and stop complaining. 

I can (and will) of course do that, but since I believe my fix is of 
interest not only to us, but others who setup their environment 
using the .templateconf file, my primary goal is to try to improve 
upstream first.

> I have a large amount of
> manual recipe updates I need to do, because no one else wants to do
> it, and so I will not be arguing with you anymore.
> 
> Alex

//Peter

> On Tue, 27 Sept 2022 at 17:29, Alexander Kanavin via
> lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
> wrote:
> >
> > On Tue, 27 Sept 2022 at 16:56, Peter Kjellerstedt
> > <peter.kjellerstedt@axis.com> wrote:
> > > Since I of course do not want for my developers to face this
> > > error when they update, I have two options:
> > >
> > > 1) I can remove the old templateconf.cfg file in our wrapper.
> > >    This means I have to duplicate the code in
> > >    scripts/oe-buildenv-internal that calculates the BUILDDIR
> > >    variable. It also means I will have to keep and maintain this
> > >    code for the foreseeable future.
> > > 2) Change the code in scripts/oe-setup-builddir so that it is
> > >    not hardcoded to only support OE and Poky, but instead is
> > >    generic and works the same for anyone.
> > >
> > > From my point of view, option 2 should be the natural choice.
> >
> > Three options. You can also instruct your developers to simply remove
> > their build directories. Is that such a catastrophe? We do not promise
> > that build directories stay backwards compatible and never explode on
> > distro upgrades, we try out best, but sometimes they just don't.
> >
> > Alex
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#171107):
> https://lists.openembedded.org/g/openembedded-core/message/171107
> > Mute This Topic: https://lists.openembedded.org/mt/93847437/1686489
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
> [alex.kanavin@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >

  reply	other threads:[~2022-09-27 16:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 12:47 [PATCH 1/2] .templateconf: Mark "meta/conf" as an invalid path for templates Peter Kjellerstedt
2022-09-22 12:47 ` [PATCH 2/2] oe-setup-builddir: Do not hardcode invalid paths " Peter Kjellerstedt
2022-09-22 13:14   ` [OE-core] " Richard Purdie
2022-09-22 13:25     ` Peter Kjellerstedt
2022-09-22 15:52       ` Alexander Kanavin
2022-09-22 19:56         ` Peter Kjellerstedt
2022-09-22 20:32         ` Richard Purdie
2022-09-22 21:53           ` Alexander Kanavin
     [not found]           ` <17174D5BCC8D1164.8129@lists.openembedded.org>
2022-09-26 17:09             ` Alexander Kanavin
2022-09-27 14:56           ` Peter Kjellerstedt
2022-09-27 15:29             ` Alexander Kanavin
     [not found]             ` <1718C14CEB633922.9698@lists.openembedded.org>
2022-09-27 15:42               ` Alexander Kanavin
2022-09-27 16:06                 ` Peter Kjellerstedt [this message]
2022-09-27 16:16                   ` Alexander Kanavin
2022-09-27 18:53                     ` Peter Kjellerstedt
2022-09-27 19:58                       ` Alexander Kanavin
2022-09-27 21:31                         ` Peter Kjellerstedt
2022-09-27 21:50                           ` Alexander Kanavin
2022-09-28  9:54                             ` Peter Kjellerstedt
2022-09-28 10:59                               ` Alexander Kanavin
2022-09-28 12:45                                 ` Peter Kjellerstedt
2022-09-28 13:24                                   ` Alexander Kanavin
     [not found]                               ` <17190128C53AF22E.9603@lists.openembedded.org>
2022-09-28 11:05                                 ` Alexander Kanavin
2022-09-27 17:04                   ` Alexander Kanavin
2022-09-27 19:22                     ` Peter Kjellerstedt
2022-09-27 20:39                       ` Alexander Kanavin

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=faab0d74b95849bdb1d39ac0146dd523@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.