bazelbuild/bazel

Add option to create bazel symlinks using relative paths (instead of absolute)

Open

#2,351 opened on Jan 9, 2017

View on GitHub
 (11 comments) (10 reactions) (0 assignees)Java (25,384 stars) (4,465 forks)batch import
P3help wantednot staleteam-OSStype: feature request

Description

It'd be nice if the set of symlinks created by bazel (i.e. bazel-bin, bazel-genfiles, etc) had to option to use relative paths instead of absolute paths. In our case, this makes it easier to work off an NFS export and use OS-native tools on the files in that export.

Contributor guide

Tech stack
java
Domain
build system
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Bazel build system basicsJavaSymbolic links
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the existing discussion in issue comments (11 comments) to understand previous proposals or concerns. Examine Bazel's source code, particularly the logic that creates symlinks (e.g., in the file system abstraction layer) to identify where to add a relative path option. Look for files like src/main/java/com/google/devtools/build/lib/... that handle workspace symlinks.