Skip to content

Modules obtained from registries should fall back to copying MODULE.bazel from the registry #26217

@gholms

Description

@gholms

Description of the feature request:

For modules representing projects which lack MODULE.bazel files, module maintainers have to carry patch files or overlay/MODULE.bazel symlinks so http_archive and friends take care of injecting them into repos. Since the registry already needs to contain MODULE.bazel anyway, this amounts to needless busywork for nearly every module in the BCR. When a module comes from a registry, bazel should fall back to copying or symlinking the MODULE.bazel file it got from the registry if none exists after repository rules finish.

Which category does this issue belong to?

External Dependency

What underlying problem are you trying to solve with this feature?

Needless busywork for most modules' maintainers.

Which operating system are you running Bazel on?

Ubuntu 20.04

What is the output of bazel info release?

release 7.6.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?


Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

Metadata

Metadata

Assignees

Labels

P1I'll work on this now. (Assignee required)team-ExternalDepsExternal dependency handling, remote repositiories, WORKSPACE file.type: feature request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions