The setup-ds.pl and setup-ds-admin.pl scripts still seem to require perl-mozilla-ldap even if built --with-openldap.
389-ds-base 1.4.0.2-1 built from source on Arch Linux
See:
use Mozilla::LDAP::Conn; use Mozilla::LDAP::Utils qw(normalizeDN); use Mozilla::LDAP::API qw(ldap_explode_dn); use Mozilla::LDAP::LDIF;
Not finding references to Mozilla:LDAP
We are planning on moving to a python installer for 1.4.0, but until that is done, regardless if "--with-openldap" is set, we must still use perLDAP (perl-Mozilla-LDAP) for these perl scripts.
"--with-openldap" was designed to specify what client library the core server would use (mozilla or openldap). It was not intended to impact the scripts, or completely remove the "mozilla" dependency from the package.
Anyway, I think the work on the new python installer is almost complete - it just has not been committed yet as we've all been busy wrapping up work on 1.3.7. That being said, for now we will probably still need perldap for other CLI tools like register-ds-admin.pl.
We do want to get rid of all the perl (which would remove the perldap requirement) in 1.4.0, but that work has not really begun yet, so no promises.
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Sounds like I need to get back to trying to make mozldap build on Arch, again. I think it's been broken for a while.
@imntreal How soon do you need this packaged by? If you were willing, you could pass in "--disable-perl" to the ./configure, and try to use our python3 tools instead. The create/remove of the server is pretty solid today, and we can already run the majority of our test cases with them.
If you are not in a rush to package this, it would be good for you to do this the "future" way, rather than spending a lot of time on this when we are just going to deprecate it so soon.
I would prefer using the new method, and helping test the "future" way. I'm already running 1.4.0.2. Apparently, between upgrading to 1.4.0.1, and .2, I got rid of the Mozilla LDAP packages, and now they won't build. The only functionality I need personally is the update functionality provided by the setup scripts. I haven't seen any mention of a straight forward way to do that with the python tools. Is there already a python script written that provides that function?
There have been no "update" scripts provided in a long time, and there is no plan to add them into the python. Instead the current design idea is to integrate this into server core so that upgrades happen at "startup" instead. This is so that it works correctly in containers.
So there is no equivalent to setup-ds.pl -u, because it won't be needed. You only need the python tools for creating the instance and that's it. :)
If you need more guidance I can write something up on how to use these. The current wiki pages are a little outdated so I should update this I think
Going to close this as we are about to release the python tools and there is no work for us to do here.
These will be annouced on our 389-devel list and will be in 1.4.x.
Thanks,
Metadata Update from @firstyear: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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/2501
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.
Login to comment on this ticket.