From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 3/3] meta: Manual override fixes
Date: Wed, 28 Jul 2021 21:24:48 +0100 [thread overview]
Message-ID: <ca0a10a951237a41cda24eefa7300ea646f98c23.camel@linuxfoundation.org> (raw)
In-Reply-To: <16960CD0F3F5D3AD.12099@lists.openembedded.org>
On Wed, 2021-07-28 at 21:00 +0100, Richard Purdie via lists.openembedded.org wrote:
> On Wed, 2021-07-28 at 12:32 -0700, Andre McCurdy wrote:
> > On Wed, Jul 28, 2021 at 7:15 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > >
> > > The automated conversion of OE-Core to use the new override sytax isn't
> > > perfect. This patches some mis-converted lines and some lines which were missed
> > > by the automation.
> > >
> > > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > @@ -86,7 +86,7 @@ python systemd_populate_packages() {
> > > bb.debug(1, 'adding systemd calls to postinst/postrm for %s' % pkg)
> > >
> > > paths_escaped = ' '.join(shlex.quote(s) for s in d.getVar('SYSTEMD_SERVICE:' + pkg).split())
> > > - d.setVar('SYSTEMD_SERVICE:ESCAPED_' + pkg, paths_escaped)
> > > + d.setVar('SYSTEMD_SERVICE_ESCAPED:' + pkg, paths_escaped)
> >
> > This is manually fixing the misconversion of _ESCAPED to :ESCAPED,
> > right? If so then does it mean a bug in the automatic conversion
> > script since overrides can't be uppercase?
>
> There are several bugs in the script, yes. The question is how far to go
> in trying to address them and this wasn't a common issue.
In case it isn't clear, this isn't as easy as you might first think. We need
to convert SYSTEMD_SERVICE_${PN} which has uppercase characters in it. Can it
be fixed? Probably, yes. Is it worth the effort/complexity? Maybe not.
Cheers,
Richard
next prev parent reply other threads:[~2021-07-28 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 14:15 [PATCH 1/3] scripts/contrib: Add override conversion script Richard Purdie
2021-07-28 14:15 ` [PATCH 2/3] Convert to new override syntax Richard Purdie
2021-07-28 14:15 ` [PATCH 3/3] meta: Manual override fixes Richard Purdie
2021-07-28 19:32 ` [OE-core] " Andre McCurdy
2021-07-28 20:00 ` Richard Purdie
[not found] ` <16960CD0F3F5D3AD.12099@lists.openembedded.org>
2021-07-28 20:24 ` Richard Purdie [this message]
2021-07-28 20:43 ` Andre McCurdy
2021-07-28 20:53 ` Richard Purdie
2021-07-28 21:21 ` Andre McCurdy
2021-07-28 21:28 ` Richard Purdie
[not found] ` <169611A4DF65986F.13113@lists.openembedded.org>
2021-07-28 22:42 ` Richard Purdie
2021-07-28 14:52 ` [OE-core] [PATCH 1/3] scripts/contrib: Add override conversion script Michael Opdenacker
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=ca0a10a951237a41cda24eefa7300ea646f98c23.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.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.