[SERVER-24446] Determine which packages are go system vs. part of current build Created: 07/Jun/16 Updated: 06/Dec/22 Resolved: 14/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Justin Cohler | Assignee: | DO NOT USE - Backlog - Dev Tools |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Developer Tools
|
| Sprint: | Platforms 16 (06/24/16) |
| Participants: |
| Description |
|
Logic to determine which packages are go system vs. part of current build: (Use go list command) |
| Comments |
| Comment by bdbaddog#1 [ 29/Jul/16 ] |
|
Retrieving project and system packages (at least for google go) working. Need to resolve how to do so with google go (it doesn't find any system packages). Need to avoid looking for them in GOPATH (in project) so that proper go source files added to DAG for packages. |