<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 09:08:03 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[MONGOCRYPT-139] kms_message cmake cleanup</title>
                <link>https://jira.mongodb.org/browse/MONGOCRYPT-139</link>
                <project id="17481" key="MONGOCRYPT">Libmongocrypt</project>
                    <description>&lt;p&gt;Let&apos;s audit the CMakeLists.txt of kms_message. I&apos;m hazy on how the install targets and package configuration work.&lt;/p&gt;

&lt;p&gt;kms_message won&apos;t (for now) be distributed as a separate library. It will be statically linked with libmongocrypt. Really, we just need it to work well enough so we can statically link against it everywhere we build libmongocrypt. This ticket might be a no-op, but let&apos;s at least spend some time double checking this.&lt;/p&gt;</description>
                <environment></environment>
        <key id="700687">MONGOCRYPT-139</key>
            <summary>kms_message cmake cleanup</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="13203">Gone away</resolution>
                                        <assignee username="roberto.sanchez@mongodb.com">Roberto Sanchez</assignee>
                                    <reporter username="kevin.albertson@mongodb.com">Kevin Albertson</reporter>
                        <labels>
                    </labels>
                <created>Tue, 19 Feb 2019 19:29:45 +0000</created>
                <updated>Fri, 27 Oct 2023 19:41:36 +0000</updated>
                            <resolved>Fri, 17 May 2019 14:23:33 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="2250800" author="roberto.sanchez" created="Fri, 17 May 2019 18:00:44 +0000"  >&lt;p&gt;So, having a SONAME now would make future changes easier, since adding a SONAME where there was not previously one can be somewhat disruptive from a build/deployment perspective.  In my mind, it is better to cause that disruption before the first release.  Additionally, if we are still entertaining the possibility of packaging for Debian and/or Fedora, both of those distributions will require that the library carry a proper SONAME.&lt;/p&gt;

&lt;p&gt;I recommend creating a new ticket and blocking &lt;a href=&quot;https://jira.mongodb.org/browse/MONGOCRYPT-76&quot; title=&quot;libmongocrypt: package for Debian&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MONGOCRYPT-76&quot;&gt;&lt;del&gt;CDRIVER-2971&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://jira.mongodb.org/browse/MONGOCRYPT-108&quot; title=&quot;libmongocrypt: package for Fedora&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MONGOCRYPT-108&quot;&gt;&lt;del&gt;CDRIVER-2972&lt;/del&gt;&lt;/a&gt; with it.&lt;/p&gt;</comment>
                            <comment id="2250774" author="kevin.albertson" created="Fri, 17 May 2019 17:49:43 +0000"  >&lt;blockquote&gt;
&lt;p&gt;not shipping any kms_message components&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;We do need to ship the shared kms_message for shell. Unless there&apos;s a reason, I don&apos;t think it hurts to ship both static/shared kms_message, unless you mean something else.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;possibly adding more sensible versioning/SONAME support to libmongocrypt (assuming that it is desirable to support more robust dynamic linking of libmongocrypt)&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Hmm, maybe we do need to do this before releasing. Though we should probably aim to keep things ABI stable, if we do make an ABI break later, I imagine it&apos;ll be less destructive if we have an SONAME in place, but I&apos;m also not super familiar with this. Should we create a separate ticket?&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                            <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>CDRIVER-2915</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|huotpz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>