On Wednesday, 2 December 2020 05:22:43 NZDT Martin Jansa wrote:
> I see, I was just worried that this case will block me pushing the last bit
> of [YOCTO #12937] which changes symlinks to hardlinks:
> https://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/artifact
> s
>
> Which makes
Hi Paul,
I see, I was just worried that this case will block me pushing the last bit
of [YOCTO #12937] which changes symlinks to hardlinks:
https://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/artifacts
Which makes the use case you're fixing worse (as even less systems will
correct
Hi Martin
(replying all this time)
On Tuesday, 1 December 2020 15:40:36 NZDT you wrote:
> Can we use a separate variable controlling this behavior other than
> *_LINK_NAME variables being set to empty?
>
> Then we could easily extend it to stop creating the links also for image
> artifacts as wel
Can we use a separate variable controlling this behavior other than
*_LINK_NAME variables being set to empty?
Then we could easily extend it to stop creating the links also for image
artifacts as well.
On Thu, Nov 26, 2020 at 7:55 PM Paul Eggleton <
bluelightn...@bluelightning.org> wrote:
> On T
On Thursday, 26 November 2020 14:01:47 NZDT Paul Eggleton wrote:
> From: Paul Eggleton
>
> Allow setting any of the *_LINK_NAME variables to empty string in order
> to disable creating symlinks. This is particularly useful for situations
> where symlinks in DEPLOY_DIR_IMAGE will be treated extern
From: Paul Eggleton
Allow setting any of the *_LINK_NAME variables to empty string in order
to disable creating symlinks. This is particularly useful for situations
where symlinks in DEPLOY_DIR_IMAGE will be treated externally as
duplicates of the linked files (in which case you would probably se
