[MONGOCRYPT-182] Reconsider how libmongocrypt is obtained Created: 24/Sep/19 Updated: 27/Oct/23 Resolved: 31/Oct/19 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Albertson | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Description |
|
Currently, Go driver users are advised to clone and compile libmongocrypt using the included compile.sh script here: This means users need to compile and install libbson (and cannot rely on system libbson), are relying on the master branch to be stable, and that compile.sh is no longer internal. Let's reconsider our strategy for having users of the Go driver (and perhaps other drivers) obtain libmongocrypt. Perhaps directing users get libmongocrypt through packages (e.g. |
| Comments |
| Comment by Kevin Albertson [ 31/Oct/19 ] |
|
Decision: Before GA:
And will add libmongocrypt to homebrew. |
| Comment by Githook User [ 24/Sep/19 ] |
|
Author: {'name': 'Kevin Albertson', 'username': 'kevinAlbs', 'email': 'kevin.albertson@mongodb.com'}Message: |