Since the implementation of the entryuuid plugin rust and cargo have to be enabled, otherwise the libraries will not be built and there are errors at startup:
[09/Jun/2020:09:16:46.352808516 +0200] - ERR - symload_report_error - Netscape Portable Runtime error -5977: .../install/lib/dirsrv/plugins/libentryuuid-syntax-plugin.so: cannot open shared object file: No such file or directory [09/Jun/2020:09:16:46.411212573 +0200] - ERR - symload_report_error - Could not open library ".../install/lib/dirsrv/plugins/libentryuuid-syntax-plugin.so" for plugin entryuuid_syntax [09/Jun/2020:09:16:46.444495884 +0200] - ERR - slapd_bootstrap_config - The plugin entry [cn=entryuuid_syntax,cn=plugins,cn=config] in the configfile ...install/etc/dirsrv/slapd-master1/dse.ldif was invalid. Failed to load plugin's init function.
Question is also why is the entryuuid-plugin deployed vis bootstrap config and not in the template dse.ldif ?
It's meant to be ifdef'd out? I don't understand why that's happening. I'll look tomorrow :( :( :(
Metadata Update from @firstyear: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
building it is ifdefed out, but slapd_bootstrap_config() always will try to load it
Sorry I didn't get to look today - some things came up at SUSE. It'll be priority number 1 tomorrow mate :)
https://pagure.io/389-ds-base/pull-request/51146 @elkris
The patch will fix the issue, but I still am not very happy with it. It ties the availability of a feature, entryuuid-plugin, to a language enabled, so it is the decision of the builder and not the adminb deploying the server. And if we have another feature requiring rust, they will get the plugin automatically, enabled, without asking for it.
In my opinon, as the subject of the issue says, we have come to a point where rust is no longer optional, it is a must, like gcc or python.
So I would prefer enablingrust by default, get rid of the ifdefs, but disable the plugin by default (if it has to be in bootstrap_config or in template dse.ldif is another question).
I'm going to open up a mail on 389-devel, because I think you raise good points here, and I think there is a short todo of things that need to be done before we say "lets go" on rust by default. It is probably easier to discuss on mail.
Thanks mate :)
Metadata Update from @mreynolds: - Issue priority set to: major - Issue set to the milestone: 1.4.4
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/4193
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.