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

Add RunfilesLibraryInfo provider #16077

Closed
wants to merge 1 commit into from

Conversation

fmeum
Copy link
Collaborator

@fmeum fmeum commented Aug 10, 2022

The new Starlark-defined RunfilesLibraryInfo provider may be used in the
future to decide whether additional information has to be emitted by a
rule for a target to find its runfiles at runtime. This may include
serializing repository mapping information to a runfile and/or
generating code that provides the canonical name of the current
repository.

The provider is added now rather than later so that third-party runfiles
libraries can rely on it being present earlier - they have to wait for
their minimum supported Bazel version to offer it. If it should turn out
not to be needed, it can safely be removed before any ruleset would have
a reason to depend on it.

Work towards bazelbuild/proposals#269

@fmeum fmeum marked this pull request as ready for review August 10, 2022 09:45
@sgowroji sgowroji added team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website awaiting-review PR is awaiting review from an assigned reviewer labels Aug 10, 2022
The new Starlark-defined RunfilesLibraryInfo provider may be used in the
future to decide whether additional information has to be emitted by a
rule for a target to find its runfiles at runtime. This may include
serializing repository mapping information to a runfile and/or
generating code that provides the canonical name of the current
repository.

The provider is added now rather than later so that third-party runfiles
libraries can rely on it being present earlier - they have to wait for
their minimum supported Bazel version to offer it. If it should turn out
not to be needed, it can safely be removed before any ruleset would have
a reason to depend on it.

Work towards bazelbuild/proposals#269
@fmeum
Copy link
Collaborator Author

fmeum commented Aug 10, 2022

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Aug 10, 2022
@fmeum
Copy link
Collaborator Author

fmeum commented Aug 10, 2022

@oquenchil I just realized that it might be problematic for builtins to access a provider defined in @bazel_tools. Do you see a way to add a Starlark-defined provider to Bazel that can be loaded by third-party rulesets but still be usable from builtin rules such as cc_library? If not, then RunfilesLibraryInfo would probably have to be a native provider.

@fmeum fmeum marked this pull request as draft August 10, 2022 13:20
@ShreeM01
Copy link
Contributor

Hi @fmeum! This PR is in draft state, Can you please provide an update on this since we are very close to our release date. Thanks!

@fmeum
Copy link
Collaborator Author

fmeum commented Aug 12, 2022

@kshyanashree I am stuck and looking for feedback from @oquenchil. If I don't get this done in time, please just ignore this PR.

@sgowroji sgowroji removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Aug 16, 2022
@fmeum fmeum closed this Aug 17, 2022
@fmeum fmeum deleted the runfiles-library-info branch August 17, 2022 16:27
@ShreeM01 ShreeM01 removed the awaiting-review PR is awaiting review from an assigned reviewer label Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants