Thus spake Rasmus Wiman on Fri, Jun 09, 2006 at 07:57:21PM CDT > Lindsay Haisley <[EMAIL PROTECTED]> wrote: > > > advantage of them. Perhaps rather than a single "ldap" USE flag, > > there need to be at least a couple - "ldap-auth", "ldap-client", etc. > > Isn't there some file in /etc/portage called packages.use or something > like that, which achieves this goal by explicitly setting use flags on > a per-package basis. You could either have > > mail-client/evolution +ldap > > or > > sys-apps/pam-login -ldap > > in there, thus solving the problem without any extra use flags. I > haven't used it, but heard of such a file and I guess it would solve > your problem.
Yes, the file is /etc/portage/package.use and I make use of it a lot, no pun intended ;-) Using this file is kind of a "backup fix" for the problem, and I do indeed have -ldap on several system utilities that shouldn't use it. The problem is that trying to guess this stuff before hand and control it with USE flags is really shooting in the dark. Who would have thought, for instance, that udevd would have indirectly ended up depending on finding an active ldap server on a booting system! Look at /usr/portage/profiles/use.desc though, it doesn't seem that my way of thinking on this goes along with how the USE flags have evolved, so I guess I'll just drop it. -- Lindsay Haisley | "Everything works | PGP public key FMP Computer Services | if you let it" | available at 512-259-1190 | (The Roadie) | <http://www.fmp.com/pubkeys> http://www.fmp.com | | -- [email protected] mailing list
