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 could imagine introducing a data attribute next to srcs, but it would be a breaking change to stop including the srcs in runfiles so I'm not sure that's feasible.
That’s a good idea.
Our current workaround is to have a custom rule that removes all runfiles from a target (we’re copying only C++ source files in our case)
What happened?
When I use
copy_to_directory
in any step of my build, all copied files get included into archives generated withpkg_tar
andinclude_runfiles=True
. This makes it so, in addition to our binaries, we also get source files in the archive.This is because all files are added to the
runfiles
member ofDefaultInfo
: https://github.com/aspect-build/bazel-lib/blob/71a80525891942267bf1335d830652a0115dcfce/lib/private/copy_to_directory.bzl#L294C28-L294C36Would it be possible to add an attribute to control whether files are added to runfiles or not?
Version
Development (host) and target OS/architectures: SUSE SLE RT 15 SP4
Output of
bazel --version
: bazel 6.5.0Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file: 1.37.0Language(s) and/or frameworks involved:
How to reproduce
No response
Any other information?
No response
The text was updated successfully, but these errors were encountered: