From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/containerd: security bump to version 1.5.11
Date: Thu, 14 Apr 2022 22:06:59 +0200 [thread overview]
Message-ID: <87h76vbfa4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <73baff5b-2b45-446f-e910-be5a21e74c4e@mind.be> (Arnout Vandecappelle's message of "Thu, 14 Apr 2022 21:15:36 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> On a related note, the go/rust vendoring stuff isn't great for the
>> source mirror, where we basically run make foo-source for all packages -
>> And which now builds an internal toolchain and host-go / host-rust
>> before doing the download :/ I guess I'll need to rework the mirroring
>> logic a bit.
> Just don't delete the output directory?
That could kind of work if I used a per-branch output directory and
cleaned it up one in a while to not have odd behaviour when the
(dependences of) host-go / host-rust changes yeah.
I'll give it a try.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-04-14 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 17:28 [Buildroot] [git commit] package/containerd: security bump to version 1.5.11 Peter Korsgaard
2022-04-11 12:28 ` Marcus Hoffmann
2022-04-11 17:03 ` Arnout Vandecappelle
2022-04-11 18:33 ` Yann E. MORIN
2022-04-11 19:02 ` Peter Korsgaard
2022-04-11 20:27 ` Arnout Vandecappelle
2022-04-11 20:34 ` Peter Korsgaard
2022-04-12 8:28 ` Arnout Vandecappelle
2022-04-12 9:26 ` Peter Korsgaard
2022-04-14 19:15 ` Arnout Vandecappelle
2022-04-14 20:06 ` Peter Korsgaard [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=87h76vbfa4.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/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.