All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ernst Sjöstrand" <ernstp@gmail.com>
To: Marta Rybczynska <rybczynska@gmail.com>
Cc: pavel@zhukoff.net, Marta Rybczynska <marta.rybczynska@huawei.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] cve-check: move update_symlinks to a library
Date: Wed, 8 Jun 2022 11:24:25 +0200	[thread overview]
Message-ID: <CAD=4a=VUSsTgW+L561ynDOk0aStHTeVvFXRpWMTjvHS=fmrNJQ@mail.gmail.com> (raw)
In-Reply-To: <CAApg2=Q+2weQLezA040uC=OR1_9ROXYT1iEzwk4Xt1Xf91yLHQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

There's also a big create_symlinks() in image.bbclass that could use this
(partially).

//E

Den ons 8 juni 2022 kl 09:51 skrev Marta Rybczynska <rybczynska@gmail.com>:

> On Mon, Jun 6, 2022 at 8:08 AM Pavel Zhukov <pavel@zhukoff.net> wrote:
> >
> >
> > Looks like update_symplinks is widely used accros OE. Quick grepping
> gave me this:
> > [1]. I'm sure there're more occurences.
> > This should be somewhere in more accesible place (oe-core libraries).
> >
> >
>
> This is a valid point Pavel and Ernst. The patch has landed in master
> so I will do a followup.
> It seems that this could avoid a number of bugs (see the latest fix
> from Davide).
>
> Regards,
> Marta
>

[-- Attachment #2: Type: text/html, Size: 1342 bytes --]

  reply	other threads:[~2022-06-08  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  8:58 [PATCH] cve-check: move update_symlinks to a library Marta Rybczynska
2022-06-04  6:15 ` Ernst Sjöstrand
2022-06-06  6:03 ` [OE-core] " Pavel Zhukov
2022-06-08  7:51   ` Marta Rybczynska
2022-06-08  9:24     ` Ernst Sjöstrand [this message]
2022-06-08 12:27     ` Richard Purdie

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='CAD=4a=VUSsTgW+L561ynDOk0aStHTeVvFXRpWMTjvHS=fmrNJQ@mail.gmail.com' \
    --to=ernstp@gmail.com \
    --cc=marta.rybczynska@huawei.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pavel@zhukoff.net \
    --cc=rybczynska@gmail.com \
    /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.