<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/documentation/overview-manual, branch 5.2_M2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=5.2_M2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=5.2_M2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2024-10-25T14:31:57+00:00</updated>
<entry>
<title>overview-manual: concepts: add details on package splitting</title>
<updated>2024-10-25T14:31:57+00:00</updated>
<author>
<name>Antonin Godard</name>
<email>antonin.godard@bootlin.com</email>
</author>
<published>2024-10-16T12:08:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=223ae08bc60588b2fc94df4ba40a74f96c4d357f'/>
<id>urn:sha1:223ae08bc60588b2fc94df4ba40a74f96c4d357f</id>
<content type='text'>
The package splitting section of the overview manual currently lacks any
explanation of how package splitting is implemented and redirects to
the package class, which is not really understandable for newcomers to
the project.

This patch adds a short explanation of what is done:

* How the PACKAGES variable is defined.
* How the FILES variable is defined.
* How the two work together.
* How to add a custom package.

This should give enough details to a new user on what package splitting
achieves and how to add a custom package.

Adresses [YOCTO #13225]

Reviewed-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
(From yocto-docs rev: 143c3cacdec36c9d7ab81c89bbcc12c0c3936bd9)

Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>manuals: fix trailing spaces</title>
<updated>2024-04-08T13:36:38+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2024-03-30T16:52:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fed404fca0ae6eb313aeac7c029d22c06b5486a7'/>
<id>urn:sha1:fed404fca0ae6eb313aeac7c029d22c06b5486a7</id>
<content type='text'>
Fixing errors reported by "make sphinx-lint"

(From yocto-docs rev: ef6b650c31c4320314564bb85a45eebde3fd98c1)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ref-manual: variables: correct sdk installation default path</title>
<updated>2024-03-06T16:54:54+00:00</updated>
<author>
<name>Johan Bezem</name>
<email>jbezem.extern@arri.de</email>
</author>
<published>2024-02-26T16:15:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9400b992fd4c5fe14c446c44214d106b6e162971'/>
<id>urn:sha1:9400b992fd4c5fe14c446c44214d106b6e162971</id>
<content type='text'>
The SDKPATH variable seems mistakenly identified as the
default path where the SDK will be installed by the generated
installation script, unless option '-d' or a manual input
overrides this default.

The intended variable is SDKPATHINSTALL. SDKPATH indicates
where the SDK is being composed and built.

The definitions have been added/updated.

(From yocto-docs rev: d5b9c4b9c443cc728a11fd1e0a26a11aac8ee2c5)

Signed-off-by: Johan Bezem &lt;jbezem.extern@arri.de&gt;
Reviewed-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>manuals: suppress excess use of "following" word</title>
<updated>2024-02-24T16:13:28+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2024-02-09T16:48:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=025386d53ceef681d7e829ad184b6850af55619c'/>
<id>urn:sha1:025386d53ceef681d7e829ad184b6850af55619c</id>
<content type='text'>
To simplify the style, replace "Following is" and "Following are"
by "here is" and "here are", sounding more natural.

In some cases, also go further by simplifying "Here are/is xxx"
by "xxx are/is" when the "are" or "is" are not two far at
the end of the sentence.

In some cases too, completely remove the sentence, when
it's redundant with the preceding title.

(From yocto-docs rev: 52ba6bb16c73cbc2c0e77496d5226c49bce786f5)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
CC: Daniel Ammann &lt;daniel.ammann@bytesatwork.ch&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>manuals: document VSCode extension</title>
<updated>2024-01-12T11:34:05+00:00</updated>
<author>
<name>Enguerrand de Ribaucourt</name>
<email>enguerrand.de-ribaucourt@savoirfairelinux.com</email>
</author>
<published>2024-01-02T11:09:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ed6c38e3aff120a2caf817bb9fe4324979278edc'/>
<id>urn:sha1:ed6c38e3aff120a2caf817bb9fe4324979278edc</id>
<content type='text'>
The VSCode extension is now officially maintained and published by the
Yocto Project so it should be referenced in the manuals to help users
discover it.

I located the most relevant places to reference the extension by looking
at how the old Eclipse plugin was documented in the 2.6 manuals as well
as the current Toaster references.

(From yocto-docs rev: 645153504690aa8a69b028e95a5e9d2da9644cf1)

Signed-off-by: Enguerrand de Ribaucourt &lt;enguerrand.de-ribaucourt@savoirfairelinux.com&gt;
Reviewed-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>overview-manual: concepts: Add Bitbake Tasks Map</title>
<updated>2023-11-06T22:52:27+00:00</updated>
<author>
<name>BELHADJ SALEM Talel</name>
<email>bhstalel@gmail.com</email>
</author>
<published>2023-11-01T08:40:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5abd1e19451e21e59b64538d1a9ccf9fd46eba40'/>
<id>urn:sha1:5abd1e19451e21e59b64538d1a9ccf9fd46eba40</id>
<content type='text'>
Create a Map to detail how BitBake handles a recipe's tasks
and its compile/runtime dependencies along with detailed comments.

(From yocto-docs rev: 7f0ab56aa302babab6c9d600a8d8a91708cf75f7)

Signed-off-by: Talel BELHAJSALEM &lt;bhstalel@gmail.com&gt;
Reviewed-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>overview: Add note about non-reproducibility side effects</title>
<updated>2023-10-09T14:52:17+00:00</updated>
<author>
<name>Joshua Watt</name>
<email>JPEWhacker@gmail.com</email>
</author>
<published>2023-09-28T18:26:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9f64aa4afce52c9b50499e6c0a4e56732f9a800a'/>
<id>urn:sha1:9f64aa4afce52c9b50499e6c0a4e56732f9a800a</id>
<content type='text'>
Adds an additional note about some of the side effects that can occur if
recipes are not reproducible and hash equivalence is enabled.

(From yocto-docs rev: 1ccc8eefe21bc432c903bb245bd0dab06e67cc14)

Signed-off-by: Joshua Watt &lt;JPEWhacker@gmail.com&gt;
Reviewed-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>contributor guide: update instructions for making and sharing changes</title>
<updated>2023-08-30T14:54:59+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2023-08-11T17:48:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9bf8250a403e046a0cbd4bea7113b03b33b27cc0'/>
<id>urn:sha1:9bf8250a403e046a0cbd4bea7113b03b33b27cc0</id>
<content type='text'>
- Shifting the focus to multiple changes instead of just one
- Advising to create a branch for changes
- Removing unnecessary or too verbose explanations
- Adding useful resources and examples

(From yocto-docs rev: e7e47121fd979e034f8f40a043912640a6a25a5e)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>manuals: create a dedicated "Contributor Guide" document</title>
<updated>2023-08-30T14:54:59+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2023-08-02T14:01:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8a11abf6a9dac76bf9739c44102a49984e3c2977'/>
<id>urn:sha1:8a11abf6a9dac76bf9739c44102a49984e3c2977</id>
<content type='text'>
Starting from the original contents of dev-manual/changes.rst
and from text contributed by Richard Purdie.

(From yocto-docs rev: 55587d9dd009cbc92273376e0f7665b2d574d280)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>docs: fix unnecessary double white space</title>
<updated>2023-06-24T11:23:01+00:00</updated>
<author>
<name>Quentin Schulz</name>
<email>quentin.schulz@theobroma-systems.com</email>
</author>
<published>2023-06-22T16:51:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=dae1bc68986ecedaa58e8ad39ce07d92954de1d7'/>
<id>urn:sha1:dae1bc68986ecedaa58e8ad39ce07d92954de1d7</id>
<content type='text'>
There's no need for double white spaces here so let's just remove them.

Cc: Quentin Schulz &lt;foss+yocto@0leil.net&gt;
(From yocto-docs rev: e41f6689157359777c3d86d9a7afed6f9e43782b)

Signed-off-by: Quentin Schulz &lt;quentin.schulz@theobroma-systems.com&gt;
Reviewed-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
