janl opened a new issue, #142: URL: https://github.com/apache/couchdb-pkg/issues/142
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 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
