Ship search-extension files in rpm and deb server packages

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • DevProd Build
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The tarball threading does not touch yum/apt installs: the rpm specs and the debian packaging carry no extension entries, so package installs ship no extension on any platform, AL2023 included. Add the four extension files (both shared objects plus signatures) to the server package file lists (enterprise and community, per the no-edition-condition packaging decision), install path per the Scope/TD's package layout (SERVER-133863) and aligned with where the packaged mongod expects sharedLibraryPath to point. This was decided as required for 9.0 in the packaging discussions and never landed in the v9.0 specs.

      Acceptance:

      • rpm and deb file listings on affected packages show the extension pair
      • a packaged install can start mongod with the extension loaded using the shipped paths

      Part of CLOUDP-437684. Depends on SERVER-133865 (artifact threading) and SERVER-133863 (package layout).

            Assignee:
            Zac Codiamat
            Reporter:
            Evan Nixon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: