There are several sections in the openldap-2.4.21 that are disabled when the `prefix` USE flag is set. For example: use prefix || chown ldap:ldap "${EROOT}"var/run/openldap However, the group and user creation are not protected, which leads to the following warnings while emerging: * 'enewgroup()' disabled in Prefixed Portage with non root user * 'enewuser()' disabled in Prefixed Portage with non root user I've put a patched version of the ebuild in my prefix overlay [1]. [1] http://www.physics.drexel.edu/~wking/code/git/gitweb.cgi?p=wtk-prefix-overlay.git;a=blob;f=net-nds/openldap/openldap-2.4.21.ebuild;h=b68a0402a27c02a1ded74bca3a02aeab5130de79;hb=1da33e6c93ac734106a10ace79a23a1ef37f5063 Reproducible: Always Steps to Reproduce: 1. emerge -pv openldap Actual Results: ... * 'enewgroup()' disabled in Prefixed Portage with non root user * 'enewuser()' disabled in Prefixed Portage with non root user ... Expected Results: Successful install.
what's wrong with seeing the warning?
(In reply to comment #1) > what's wrong with seeing the warning? The new group/user aren't used anywhere in the ebuild (if the `prefix` use flag is set), so the ebuild should not be trying to create them. In a hypothetical system where you could create new users and groups without super user powers, the current ebuild would do so and then never use them, which makes no sense. Either commit to creating the user/group and using it, or give up on it entirely.
ok, I share your ideals, but the fact that enewuser and enewgroup already figure out themselves whether or not creating a user is possible, is sort of preparation for the day root-based prefix installs /do/ work. use prefix is simply wrong here, but we don't have something like use privileges.
OK, I'm fine with a `wontfix` then.
ok, wontfixing
