You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a build server running builds all day, long builds, such as when you are building a browser such as firefox, good luck with that.
Good thing make(1) comes in handy by only recompiling everything you've changed, or everything that has changed since the previous release in said context. Build recorder can't keep up with that currently though, if you wanted to use it to deliver an SBOM with every package, you'd be in big trouble.
The question essentially boils down to, can we do anything about that? Could we perhaps introduce a functionality which modifies an existing build-recorder.out with new data by a given build? THAT would be interesting to see.
Of course that wouldn't be as simple as appending the two files together, since we'd have to bother and remove any instances or "nodes" of files OR processes that are no longer used.
Still interesting to explore in the future.
The text was updated successfully, but these errors were encountered:
Say I am a distro maintainer.
I have a build server running builds all day, long builds, such as when you are building a browser such as firefox, good luck with that.
Good thing
make(1)
comes in handy by only recompiling everything you've changed, or everything that has changed since the previous release in said context. Build recorder can't keep up with that currently though, if you wanted to use it to deliver an SBOM with every package, you'd be in big trouble.The question essentially boils down to, can we do anything about that? Could we perhaps introduce a functionality which modifies an existing
build-recorder.out
with new data by a given build? THAT would be interesting to see.Of course that wouldn't be as simple as appending the two files together, since we'd have to bother and remove any instances or "nodes" of files OR processes that are no longer used.
Still interesting to explore in the future.
The text was updated successfully, but these errors were encountered: