public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	Ross Burton <ross@burtonini.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] should "${D}${systemd_unitdir}/system" => "${D}${systemd_system_unitdir}"?
Date: Wed, 25 Aug 2021 12:54:58 +0000	[thread overview]
Message-ID: <d555dff07d204fcda78e20c375424833@axis.com> (raw)
In-Reply-To: <37c93c88-37b0-27fd-8c25-b8edef979e73@crashcourse.ca>

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Robert P. J. Day
> Sent: den 25 augusti 2021 14:42
> To: Ross Burton <ross@burtonini.com>
> Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
> Subject: Re: [OE-core] should "${D}${systemd_unitdir}/system" =>
> "${D}${systemd_system_unitdir}"?
> 
> On Wed, 18 Aug 2021, Ross Burton wrote:
> 
> > No, yes.  systemd_system_unitdir is newer so it's used less.
> >
> > Ross
> >
> > On Wed, 18 Aug 2021 at 08:48, Robert P. J. Day <rpjday@crashcourse.ca>
> wrote:
> > >
> > >
> > >   i've (so far) run across a small number of OE recipes that use the
> > > identifier "${D}${systemd_unitdir}/system", which appears(?) to be
> > > equivalent to "${D}${systemd_system_unitdir}". is there any potential
> > > functional difference, or should this be standardized?
> 
>   please help me with basic REs ... i want to run a single perl
> command of the form
> 
>   $ perl -pi -e 's|...|...|' $(all the relevant files)
> 
> to change "${D}${systemd_unitdir}/system" ->
> "${D}${systemd_system_unitdir}"
> 
> and then eyeball it afterwards to make sure it's sane, but i can't get
> the proper combination of quotes versus backslashes. i can generate
> the list of appropriate files with:
> 
>   $ grep -rl '${systemd_unitdir}/system' *
> 
> but it's the perl expression that is defeating me. help.
> 
> rday

Just use sed, it's what it's there for:

sed -ri -e 's|\$\{systemd_unitdir\}/system|${systemd_system_unitdir}|g' **/*(.)

(the **/*(.) part only works if you use zsh, for bash you will have 
to use find and xargs instead).

//Peter


      reply	other threads:[~2021-08-25 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18  7:48 should "${D}${systemd_unitdir}/system" => "${D}${systemd_system_unitdir}"? Robert P. J. Day
2021-08-18 10:07 ` [OE-core] " Ross Burton
2021-08-18 11:54   ` Robert P. J. Day
2021-08-25 12:42   ` Robert P. J. Day
2021-08-25 12:54     ` Peter Kjellerstedt [this message]

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=d555dff07d204fcda78e20c375424833@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross@burtonini.com \
    --cc=rpjday@crashcourse.ca \
    /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