On Sun, Dec 02, 2012 at 11:16:16PM +0100, Pacho Ramos wrote > Maybe the easiest option would be to keep current defaults and simply > include a news item when libreoffice starts to pull in openldap > on a lot of systems remembering admins that they can safely enable > minimal USE flag for openldap if they won't use server capabilities
Howsabout following the same protocol as with CXX/NOCXX? In the past, portage would pick a default if neither was specified. That was changed to require a value, or else portage came to a screeching halt and spit out a message telling you that you have to set one of them. Set up 2 local USE flags "loldapsrv" and "nololdapsrv". Pseudocode... IF "loldapsrv" then build libreoffice with full ldapserver ELSE IF "nololdapsrv" then build libreoffice with ldap client libraries only, removing the server portion if it already exists ELSE stop the build and spit out an error message. Explain the 2 previous options in the error message END IF Send out a news item a week or 2 in advance, telling people to set the appropriate USE variable, and what it does. The people who read and act on news items would have no hiccups at all. Those who miss it would have a one-time inconvenience, but at least their systems wouldn't be "automagically" screwed up. -- Walter Dnes <waltd...@waltdnes.org>
