Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft: bzlmod lock file #96

Open
wants to merge 20 commits into
base: main
Choose a base branch
from

Conversation

manuelnaranjo
Copy link
Collaborator

TBD

manuelnaranjo and others added 20 commits February 2, 2025 13:19
Introducing a command capable of generating a list of  locked packages
from a set of targets and excluded packages
Now we can pass dependencies between the rpmtree instances.
Adding to the lockfile the parameters of how it got called so it can
be used to run a pin process again.
Now we can use the lock file to make bazel aware of RPMs through bzlmod
Now there's a helper in the proxy repo to pin dependencies again
Reducing the size of the lock file by relying on repositories, mirrors
and href
The format for the lock file is not yet determined
Sometimes you want to embed the bazeldnf binary into some other rule,
and for this you don't want to create rules and mess with toolchains,
instead adding a target that symlinks the target properly
Allow me to run by using the shell file in the bazel-bin directory
* Ignore recursive dependencies in RPMs because why not, RPMs are a mess
* Introduce artifacts for lock file which allows us on the MODULE.bazel
  to show the dependency tree.
Testing bzlmod CI to test the integration
When using the lockfile don't put the prefix in the alias repository
the bash script should be easier to relocate and call from ./bazel-bin
without a `bazel run`
Pass CLI arguments to bzlmod when called through bazel run or others
exposing nobest in the bzlmod lock file, same as we have in the other
commands
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant