Create RPMs for Nouveau and extend CouchDB RPM to optionally include Nouveau

rpm/SPECS/couchdb.spec.in の 99～103 行付近から始め、対応する Debian パッケージングを debian の下で比較してください。RPM が個別の Nouveau パッケージを提供する方法と、同じサーバーへのインストールと別のサーバーへのインストールで何が異なるかを追跡してください。通常のパッケージが変更されず、couchdb-nouveau が Nouveau をインストールし、local.d の設定と reload が CouchDB が利用可能な場合にのみ行われれば完了です。

The next version of CouchDB (3.4.0) will include a new component for full text search called Nouveau. Nouveau is a Java project that integrates with the rest of CouchDB which is written in Erlang.

We’d like the following scenarios to be handled:

• A user installs the regular Apache-CouchDB-3.4.0.rpm (the real name might be different) via yum install couchdb. They are not interested in Nouveau, so nothing changes for them. However, Nouveau binaries are installed on the system (this is partially already handled: https://github.com/apache/couchdb-pkg/blob/main/rpm/SPECS/couchdb.spec.in#L99-L103)
  • Same as before, but user IS interested in Nouveau, they can run yum install couchdb-nouveau on the same server and get Apache-CouchDB-Nouveau-3.4.0.rpm installed on the same system and now the following happens:
    • the installation of Nouveau creates a new config file in the CouchDB conf.d dir at /opt/couchdb/etc/local.d/nouveau.ini
    • the installation calls the /_node/_local/_config/_reload endpoint to activate the new config file, or prompts to restart CouchDB, or directly restarts CouchDB.
• A user wants to run Nouveau on a separate server, so the Apache-CouchDB-Nouveau-3.4.0.rpm installation should not try to augment the local.d config dir and reload CouchDB config, as it has no access to it.

—

We have this working for the Debian packages, look there for inspiration: https://github.com/apache/couchdb-pkg/tree/main/debian