|
Copying some recent notes from FLE meeting and slack:
- before we can package libmongocrypt in the way described, we have to package the C driver (this isn't hard from a technical perspective, as we can leverage the existing Debian and Redhat packaging)
- we will need to support RHEL, SUSE, Debian, and Ubuntu. Basically, the same as 4.2 server
- we need to know who will be managing the repository/PPA (us or someone on the server team, who might already be managing the server team's repository/PPA)
- we need to know how the packages are to be built (i.e., manually or via Evergreen)
- Via evergreen like we how we publish the rpms for mongodb
- if the packages are to be signed, we need to know who will be responsible for signing the packages (us since we will probably build them, or whomever manages the repository/PPA, which may or may not be us)
Here is the package push and signing steps: https://github.com/mongodb/mongo/blob/master/etc/evergreen.yml#L7588-L7620
|