linux/poky.git/meta/files, branch 5.2_M2

files: overlayfs-create-dirs: Improve mount unit dependency

2025-01-23T12:14:29+00:00

The RequiresMountsFor configuration option of systemd.unit (added in systemd version 201) not only adds the Requires and After options for the required mount unit, but it adds them for all mount units required to access the specified path. So this change is both a simplification, and an improvement. Not only will all needed mount units be added to Requires and After, but the overlay path does not have to be a mountpoint, but can be at any directory level beneath a mountpoint. (From OE-Core rev: fa2422232a143b21aeea3728abca82100946dbc4) Signed-off-by: Esben Haabendal Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Ross Burton

classes/ptest-python-pytest: simplify python ptest file overriding

2025-01-14T11:57:52+00:00

The complexity of overriding files from the bbclass made the behavior at times hard to follow and predict. This change replaces the default file with a heredoc equivalent that creates a default file if the user does not provide their own version of run-ptest in the SRC_URI. (From OE-Core rev: be3db5f4f1b857b93d08211019d9ff796ec389b6) Signed-off-by: Derek Straka Signed-off-by: Richard Purdie

classes/ptest-python-pytest: add a new class to consolidate pytest ptest functionality

2025-01-08T12:37:20+00:00

A large number of python packages leverage the pytest unit test framework for their ptest functionality. Currently, many of the tests have duplicate code for: 1. Installing pytest files 2. Declaring ptest dependencies 3. Script for executing tests (run-ptes) To simplify adding common pytest based ptests, added a new class enabling base functionality. Users can also override the location of the pytest files in addition to using their own version of run-ptest [RP: Minor whitespace tweaks to shell function and missing prepend space] (From OE-Core rev: d66009e608256d42b2d6573d4614a99eb13fd3f1) Signed-off-by: Derek Straka Signed-off-by: Richard Purdie

toolchain-shar-relocate.sh: fix the replacing commands

2024-12-09T15:23:28+00:00

There're two cases that the current replacing commands cannot handle well: 1. Files with whitespace in their names 2. Installation path with keyword such as 'script' This results in installation failure of a buildtools. We can use the following commands to reproduce the problem. 1. bitbake buildtools-tarball 2. ./tmp/deploy/sdk/x86_64-buildtools-nativesdk-standalone-5.1.sh -d dir-with-keyword-script -y The error message is like below: Setting it up...sed: can't read /PATH/TO/dir-with-keyword-script/sysroots/x86_64-wrlinuxsdk-linux /usr/lib/python3.13/site-packages/setuptools/_vendor/jaraco/text/Lorem: No such file or directory Failed to replace perl. Relocate script failed. Abort! The actual file name is /PATH/TO/dir-with-keyword-script/sysroots/x86_64-pokysdk-linux/usr/lib/python3.13 /site-packages/setuptools/_vendor/jaraco/text/Lorem ipsum.txt Note that the file path matches "script.*text". In fact, if we install the SDK into some directory containing both 'script' and 'text', all files will be matched. This is not expected. This patch fixes the replacing commands by doing the following two things: 1. Use '\n' as the field separator for xargs so that files with white spaces are not splitted. 2. Use awk to match the second filed of the file command's output so that the file path does not mess up with the matching process. (From OE-Core rev: 443912d512edbb75f16c52de489b33b6f8687431) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

linux-yocto: add and use GPL-2.0-with-syscall-note license

2024-12-05T17:07:10+00:00

See Linux COPYING, LICENSES/preferred/GPL-2.0 and LICENSES/exceptions/Linux-syscall-note. (From OE-Core rev: 762aecc750229047394be72ea2a5bbcb86a1cef0) Signed-off-by: Denis Osterland-Heim Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

files: Amend overlayfs unit descriptions with path information

2024-10-29T11:19:57+00:00

Having something like Starting Overlayfs directories setup /home... Starting Overlayfs directories setup /root... Finished Overlayfs directories setup /home. Finished Overlayfs directories setup /root. Mounting Overlayfs mount unit /home... Mounting Overlayfs mount unit /root... Mounted Overlayfs mount unit /root. Mounted Overlayfs mount unit /home. is much more informative than Starting Overlayfs directories setup... Starting Overlayfs directories setup... Finished Overlayfs directories setup. Finished Overlayfs directories setup. Mounting Overlayfs mount unit... Mounting Overlayfs mount unit... Mounted Overlayfs mount unit. Mounted Overlayfs mount unit. Especially as the number of overlayfs mount units increase. (From OE-Core rev: 7308b4fc6f51bdf2b8f3b7899ff3758c5968e418) Signed-off-by: Esben Haabendal Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: support tar.zst SDK_ARCHIVE_TYPE

2024-10-28T11:58:22+00:00

zst is much faster than the default xz, test result on my Precision 5680 machine: Installing a tar.xz SDK takes 37 seconds while tar.zst only takes 17 seconds. Let's introduce support for tar.zst. Also add a sanity check for supported archive types. (From OE-Core rev: 1d22562a89e91f19b818b8f9bc214be941303980) Signed-off-by: Ming Liu Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: check required tool before extracting SDK

2024-10-28T11:58:22+00:00

To extract the SDK archive, the proper tools need to be present on system, check unzip for zip archive type, check xz for tar.xz archive type. (From OE-Core rev: 718328588e832c0a59dc9b76ff4e5e3def6e8834) Signed-off-by: Ming Liu Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: replace which with "command -v"

2024-10-28T11:58:22+00:00

Command 'which' is not POSIX or even universally installed on Linux systems, replace it with 'command -v'. (From OE-Core rev: f604e059bdf0ebd23f4b9c6af3f6249c9acdc551) Signed-off-by: Ming Liu Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: exit when post-relocate-setup.sh fails

2024-10-11T11:17:02+00:00

When LD_LIBRARY_PATH is set, post-relocate-setup.sh will fail and exit properly. But such failure is ignored and the SDK installation will continue and tell user that things succeed. This is misleading. So exit immediately if post-relocate-setup.sh fails. Fixes [Yocto #15586] (From OE-Core rev: c8e2dcc1f71aa33cc6e56dfdebebbe7ef010c944) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie