mudler / mudler/luet

Explain build process relationship

Open
#340 0 comments 0 reactions 1 assignee View on GitHub

@mudler is already working on this.

Since Jul 9, 2023.

bug
Dominant language
Go
Stars
307
Forks
30
PR merge metrics
No merged PRs in 30d

Description

Luet version:
0.32.5

When building a package that has build dependencies on other packages, if anyone of these packages change in the three luet will rebuild all packages from the changes package.

Let's say we have
pkg a to d

a is base layer
b is file and requires a
c is file and requires a
d requires b and c

if b is changed Luet will rebuild c, even if c is already built and has not changed
if c is changed Luet will rebuild c as it should.

So in cases where i have 15 different packages that is required to to build a single package, if i change anyone of those packages based on what order they are listed in the required section. Luet will rebuild all ascending packages. This causes unnecessary builds. Is this how luet is suppose to function?

The following repo can be used to test this
https://github.com/krise86/luet-test
make a, b c d
change b make d (will rebuild c)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.