From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Danilo Bargen <mail@dbrgn.ch>
Cc: James Hilliard <james.hilliard1@gmail.com>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Hash verification from GitHub
Date: Mon, 17 Jan 2022 16:54:18 +0100 [thread overview]
Message-ID: <20220117155418.GE2313964@scaer> (raw)
In-Reply-To: <20220117103218.GD2313964@scaer>
Danilo, All,
On 2022-01-17 11:32 +0100, Yann E. MORIN spake thusly:
> On 2022-01-17 11:24 +0100, Danilo Bargen spake thusly:
[--SNIP--]
> > Maybe a corresponding paragraph could be added to the docs at
> > https://nightly.buildroot.org/#_integration_of_cargo_based_packages ?
> Yeah, so I already noticed that the nightly manual is not up to date...
It appears that the local tree that serves to generate the manual was
somehow corrupted, and we were only ever building the same old manual
over and over again...
It has now presumably been resolved, and [0] now reads:
A crate can depend on other libraries from crates.io or git
repositories, listed in its Cargo.toml file. Buildroot automatically
takes care of downloading such dependencies as part of the download
step of packages that use the cargo-package infrastructure. Such
dependencies are then kept together with the package source code in
the tarball cached in Buildroot’s DL_DIR, and therefore the hash of
the package’s tarball includes such dependencies.
[0] https://nightly.buildroot.org/#_infrastructure_for_cargo_based_packages
Maybe it is not so obvious and prominently advertised, indeed; patches
to improve the situation are most welcome! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-17 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 22:04 [Buildroot] Hash verification from GitHub Danilo Bargen
2022-01-16 22:14 ` James Hilliard
2022-01-16 22:37 ` Danilo Bargen
2022-01-16 22:51 ` James Hilliard
2022-01-17 10:17 ` Yann E. MORIN
2022-01-17 10:24 ` Danilo Bargen
2022-01-17 10:32 ` Yann E. MORIN
2022-01-17 15:54 ` Yann E. MORIN [this message]
2022-01-17 16:06 ` Yann E. MORIN
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=20220117155418.GE2313964@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=mail@dbrgn.ch \
/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