From: Pedro Ferreira
As a user i want to override `RUSTLIB` path on a bbclass, lets
call it `XYZ.bbclass`.
If a certain recipe inherits `cargo.bbclass` and `XYZ.bbclass` the
value of `RUSTLIB` is dependent on the order of the inherit.
If `cargo.bbclass` is inherit before `XYZ.bbclass` this will
From: Pedro Ferreira
As a user i want to override `RUSTLIB` path on a bbclass, lets
call it `XYZ.bbclass`.
If a certain recipe inherits `cargo.bbclass` and `XYZ.bbclass` the
value of `RUSTLIB` is dependent on the order of the inherit.
If `cargo.bbclass` is inherit before `XYZ.bbclass` this will
From: Pedro Ferreira
As a user i want to override `RUSTLIB` path on a bbclass, lets
call it `XYZ.bbclass`.
If a certain recipe inherits `cargo.bbclass` and `XYZ.bbclass` the
value of `RUSTLIB` is dependent on the order of the inherit.
If `cargo.bbclass` is inherit before `XYZ.bbclass` this will
From: Pedro Ferreira
As a user i want to override `RUSTLIB` path on a bbclass, lets
call it `XYZ.bbclass`.
If a certain recipe inherits `cargo.bbclass` and `XYZ.bbclass` the
value of `RUSTLIB` is depedent on the order of the inherit.
If `cargo.bbclass` is inherited before `XYZ.bbclass` this wil
Hi Ross,
Here's a simple test do reproduce it.
*Pre-conditions:*
INHERIT += "buildhistory"
BUILDHISTORY_RESET = "1"
BUILDHISTORY_PRESERVE:append = " files-in-package.txt"
*- Starting without sstate cache*
*Run:*
bitbake base-passwd
*Check:*
cat
PATH_TO_BUILD_dir/buildhistory/packages/core2-64-p
From: Pedro Ferreira
On each build using sstate-cache, buildhistory will move
content to a temporary folder named `old`.
When buildhistory looks for the main dir, it wont find it
and ends up creating it.
As a consequence how code is structured wont restore any
preserved file.
Code block moved to
The directory that buildhistory_list_pkg_files writes to during do_package
is created by do_packagedata so a clean buildhistory doesn't have
files-in-package written during the first build since packagedata happens
after do_package.
Ensure the output package folder is created to avoid missing
file
From: Richard Purdie
We planned to drop SSTATEPOSTINSTFUNC some time ago with the introduction of
postfuncs. Finally get around to doing that which should make the buildhistory
code a little more readable.
Unfortunately ordering the buildhistory function calls after the sstate ones is
difficult
This fix will ensure that, when we activate feature
`BUILDHISTORY_RESET`, files marked to keep on feature
`BUILDHISTORY_PRESERVE` will indeed exist is buildhistory
final path since they are moved to buildhistory/old but
not restored at any point.
Signed-off-by: Pedro Ferreira
Signed-off-by: Richa
From: Richard Purdie
We planned to drop SSTATEPOSTINSTFUNC some time ago with the introduction of
postfuncs. Finally get around to doing that which should make the buildhistory
code a little more readable.
Unfortunately ordering the buildhistory function calls after the sstate ones is
difficult
The directory that buildhistory_list_pkg_files writes to during do_package
is created by do_packagedata so a clean buildhistory doesn't have
files-in-package written during the first build since packagedata happens
after do_package.
Ensure the output package folder is created to avoid missing
file
This fix will ensure that, when we activate feature
`BUILDHISTORY_RESET`, files marked to keep on feature
`BUILDHISTORY_PRESERVE` will indeed exist is buildhistory
final path since they are moved to buildhistory/old but
not restored at any point.
Signed-off-by: Pedro Ferreira
Signed-off-by: Richa
This fix will ensure that, when we activate feature
`BUILDHISTORY_RESET`, files marked to keep on feature
`BUILDHISTORY_PRESERVE` will indeed exist is buildhistory
final path since they are moved to buildhistory/old but
not restored at any point.
Signed-off-by: Pedro Ferreira
Signed-off-by: Richa
From: Richard Purdie
This was deprecated with the introduction of postfunc support for tasks
in general and only used by buildhistory. Now that usage has been removed,
drop the code from sstate.bbclass. Any other users should be able to use
postfuncs too.
Signed-off-by: Richard Purdie
---
meta
The directory that buildhistory_list_pkg_files writes to during do_package
is created by do_packagedata so a clean buildhistory doesn't have
files-in-package written during the first build since packagedata happens
after do_package.
Ensure the output package folder is created to avoid missing
file
From: Richard Purdie
We planned to drop SSTATEPOSTINSTFUNC some time ago with the introduction of
postfuncs. Finally get around to doing that which should make the buildhistory
code a little more readable.
Unfortunately ordering the buildhistory function calls after the sstate ones is
difficult
The directory that buildhistory_list_pkg_files writes to during do_package
is created by do_packagedata so a clean buildhistory doesn't have
files-in-package written during the first build since packagedata happens
after do_package.
Ensure the output package folder is created to avoid missing
file
From: Richard Purdie
This was deprecated with the introduction of postfunc support for tasks
in general and only used by buildhistory. Now that usage has been removed,
drop the code from sstate.bbclass. Any other users should be able to use
postfuncs too.
Signed-off-by: Richard Purdie
(cherry p
This fix will ensure that, when we activate feature
`BUILDHISTORY_RESET`, files marked to keep on feature
`BUILDHISTORY_PRESERVE` will indeed exist is buildhistory
final path since they are moved to buildhistory/old but
not restored at any point.
Signed-off-by: Pedro Ferreira
Signed-off-by: Richa
From: Richard Purdie
We planned to drop SSTATEPOSTINSTFUNC some time ago with the introduction of
postfuncs. Finally get around to doing that which should make the buildhistory
code a little more readable.
Unfortunately ordering the buildhistory function calls after the sstate ones is
difficult
Hi Richard,
Applying your patches plus the buildhistory patches, files-in-package.txt
generated successfully but I noticed that latest file now is missing (from a
fresh build).
As far as I could see, it exits buildhistory_emit_pkghistory() execution from a
silent exception when it tries to open
Hi Richard,
I tried to pickup your patch and make it fit but unsuccessful. Would this be an
alternative only for LTS branches?
Thanks,
Pedro
From 3ab48da7a94b80bb67ebef5a06d92ace134e0bbf Mon Sep 17 00:00:00 2001
From: Pedro Ferreira
Date: Thu, 29 Aug 2024 11:37:19 +0100
Subject: [PATCH] sstat
] buildhistory: fix package output folder
creation
Notice: This e-mail has originated from an external email service, so do not
click on any links, nor open any attachments unless you know who the sender is
and are sure the content is secure.
On Tue, Aug 13, 2024 at 1:05 AM Pedro Ferreira via
Is it possible/feasible to backport this change to LTS branches
Thank you,
Pedro Ferreira
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#203258):
https://lists.openembedded.org/g/openembedded-core/message/203258
Mute This Topic: https://lists.ope
Hi,
Yes I can see the issue using poky[master] on commit
`db87ca070c5a4790dcdb9601bcb35037603f6d7f`.
For each package inside recipe_package I can only see latest and
latest.pkg_postinst/preinst if applicable. There should be a
files-in-package.txt for each package, but as I mentioned, the `reci
This fix will ensure that, when we activate feature
`BUILDHISTORY_RESET`, files marked to keep on feature
`BUILDHISTORY_PRESERVE` will indeed exist is buildhistory
final path since they are moved to buildhistory/old but
not restored at any point.
Signed-off-by: Pedro Ferreira
---
v2 changes:
Fix
This fix garantees that output package folder exists on
buildhistory folder to avoid missing files-in-package.txt
creation during task `package` execution.
This issue happens because the output folder is being
created on task `packagedata` before generating `latest` file.
Also it ensures that in
reation
Notice: This e-mail has originated from an external email service, so do not
click on any links, nor open any attachments unless you know who the sender is
and are sure the content is secure.
On Fri, 2024-08-02 at 15:00 +0100, Pedro Ferreira via lists.openembedded.org
wrote:
>
This fix will ensure that, when we activate feature
`BUILDHISTORY_RESET`, files marked to keep on feature
`BUILDHISTORY_PRESERVE` will indeed exist is buildhistory
final path since they are moved to buildhistory/old but
not restored at any point.
Signed-off-by: Pedro Ferreira
---
meta/classes/bu
This fix garantees that output package folder exists on
buildhistory folder to avoid missing files-in-package.txt
creation during task `package` execution.
This issue happens because the output folder is being
created on task `packagedata` before generating `latest` file.
Also it ensures that in
30 matches
Mail list logo
