Summary: | circular dependency between pam and xfree when using USE="X pam" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | E. Papegaaij <epapegaaij> |
Component: | [OLD] Core system | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo, jan.brezina, pam-bugs+disabled |
Priority: | High | ||
Version: | 1.4 | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.mail-archive.com/gentoo-user%40gentoo.org/msg28498.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | xfree-4.3.0-r5.ebuild.pam-fix.diff |
Description
E. Papegaaij
2003-12-09 12:39:12 UTC
Any ideas here? the source of pam depending on xfree goes down to python depending on 'tk' when USE=tcltk Anyone see an option besides disabling xfree's USE=pam? *** Bug 39433 has been marked as a duplicate of this bug. *** OK, our options here seem to be this: 1) Disable xfree's PAM -- this means PAM-based XDM authentication won't work, although the "standard" way will. 2) Disable python's tk interface. 3) Figure out some way to force people to disable USE=pam on first xfree merge but not latter ones, using has_version and re-exporting USE with a warning or similar. Since pam is in "system," we shouldn't need to list a dependency on it, AFAICT. Even though 3) is hackish, it's the best thing I can think of. Created attachment 25697 [details, diff]
xfree-4.3.0-r5.ebuild.pam-fix.diff
OK I don't like this but it's the best I can think of.
Fixed in 4.3.0-r6. PAM doesn't depend on Python anyway... at least not according to DEPEND. If it does, but this is a bug, can this be changed to somehow have PAM require recompilation instead of X? I am having the same bug with my xorgs libraryes, and cant solve trought that fix package. You won't be able to, considering the fix is for a package 2 years old :P If you're having a problem now it's likely a different problem altogether. Please file a new bug. |