From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: "Frederic Martinsons" <frederic.martinsons@gmail.com>
Cc: Martin Jansa <martin.jansa@gmail.com>,
akuster <akuster@mvista.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH] fetch2: Display all missing checksum at once
Date: Wed, 05 Apr 2023 11:39:56 +0200 [thread overview]
Message-ID: <lysfded5w3.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CA+cAkeqJmpO2A6-bERPJjTuKt+e-MLBAgtFB34UOSRCb=7hBMw@mail.gmail.com> (Frederic Martinsons's message of "Wed, 5 Apr 2023 07:20:16 +0200")
"Frederic Martinsons" <frederic.martinsons@gmail.com> writes:
> I looked at the suricata recipe in meta-security and it didn't use
> cargo-update-recipes.bbclass
>
> You should modify your rust recipes to use this class and have access to
> "bitbake -c update_crates" .
Is this really the recommended way for rust packages? As you already
mentioned, this has a big problem with bootstrapping: fetch (for
downloading the crates) and compile (to create Cargo.lock) must be
run before do_update_crates works.
IMO, the crate fetcher should be changed to create versioned 'name'. Then
the 'cargo bitbake' output can be used directly and missing checksums can
be copied & pasted.
Enrico
next prev parent reply other threads:[~2023-04-05 9:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 15:21 [PATCH] fetch2: Display all missing checksum at once frederic.martinsons
2023-04-04 16:49 ` [bitbake-devel] " akuster
2023-04-04 17:07 ` Frédéric Martinsons
2023-04-04 20:43 ` akuster
2023-04-04 17:07 ` Martin Jansa
2023-04-04 21:08 ` akuster
2023-04-04 21:35 ` Martin Jansa
2023-04-05 5:20 ` Frédéric Martinsons
2023-04-05 9:39 ` Enrico Scholz [this message]
2023-04-05 9:51 ` Frédéric Martinsons
2023-04-05 10:14 ` Enrico Scholz
2023-04-05 10:49 ` Frédéric Martinsons
2023-04-05 11:38 ` akuster
2023-04-05 12:25 ` akuster
2023-04-05 12:51 ` Frédéric Martinsons
2023-04-05 16:26 ` akuster808
2023-04-05 16:32 ` Frédéric Martinsons
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=lysfded5w3.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=akuster@mvista.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=frederic.martinsons@gmail.com \
--cc=martin.jansa@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.