From: "BELHADJ SALEM Talel" <talel.hajsalem@sofia-technologies.com>
To: docs@lists.yoctoproject.org
Subject: Re: Yocto Tasks Detailed Diagram Proposal
Date: Thu, 22 Jun 2023 04:34:32 -0700 [thread overview]
Message-ID: <18651.1687433672747999997@lists.yoctoproject.org> (raw)
In-Reply-To: <85e61da1-26b2-1f9e-2170-ba336b3e78c0@theobroma-systems.com>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Hello Quentin,
Thanks for your reply,
>
> what this is supposed to represent or in which scenario this would be a
> diagram
The diagram is the detailed process of how bitbake will handle building a recipe that depends on other recipe, and show the details of the working directory of a recipe which I noticed that lot of Yocto developers get confused with.
>
> I've seen you've continued to post a few things here and there on LinkedIn
> too, nice :)
I have lot of contributions in mind: diagrams, documentation, classes, new bitbake binary ideas based on Bitbake python library, for example you can have a look at : bitbake-recipe which looks for all recipes that start with a given input, and show its path, version, and other information (Covering limitation of devtool and bitbake-layers on the topic of looking for recipes): GitHub link: https://github.com/bhstalel/bitbake-recipe
I would like to start contributing, but I need a quick meeting with a contributor to explain to me the meetings, patch sending process ,... etc
I will take your comments about " *sysroot-destdir* " into consideration and I will start fixing the diagram and prepare the SVG format.
Thanks,
Talel
[-- Attachment #2: Type: text/html, Size: 1562 bytes --]
next prev parent reply other threads:[~2023-06-22 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 17:13 Yocto Tasks Detailed Diagram Proposal Bel Hadj Salem Talel
2022-11-01 15:42 ` [docs] " Michael Opdenacker
2023-06-22 9:08 ` Quentin Schulz
2023-06-22 11:34 ` BELHADJ SALEM Talel [this message]
2023-10-17 18:56 ` BELHADJ SALEM Talel
2023-10-19 14:29 ` [docs] " Michael Opdenacker
2023-10-20 18:03 ` Talel BELHADJ SALEM
2023-10-27 8:17 ` Michael Opdenacker
2023-10-27 12:18 ` Talel BELHADJ SALEM
2023-10-27 15:02 ` Michael Opdenacker
2023-10-27 15:31 ` Talel BELHADJ SALEM
[not found] ` <178FE2DDDBFED311.11247@lists.yoctoproject.org>
2023-10-27 7:27 ` Talel BELHADJ SALEM
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=18651.1687433672747999997@lists.yoctoproject.org \
--to=talel.hajsalem@sofia-technologies.com \
--cc=docs@lists.yoctoproject.org \
/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