Summary: | xlockmore ebuild has got problems | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cedric Meury <cedric.meury> |
Component: | New packages | Assignee: | Seemant Kulleen (RETIRED) <seemant> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 1.0 RC6 r14 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
The thing about unmering had nothing to do with xlockmore, forget that, sorry for any inconveniences. But the --enable-xlockrc still is a problem. Ok, sorry for the various changes on this bug, I have found the problem now and fixed it. Don't use --enable-pam. Fix: 1) delete line 22 which says: use pam && myconf="--enable-pam" 2) on line 30, add: myconf="${myconf} --enable-xlockrc" Then it'll compile fine, with shadow password support. The pam line should _not_ be removed. What you may wish to do instead is one of two things: export USE="-pam" ; emerge xlockmore or if you never want pam support, put "-pam" in your USE string in /etc/make.conf As for the other thing, I will have a look. OK, I have added a test to the ebuild -- if "pam" is not in your USE string, then it will enable xlockrc instead. |
The apps-misc/xlockmore ebuild (r3) has got some serious problems. Firstly, shadow password support is not compiled in by default. Add --enable-xlockrc to the configure script as a parameter. When I do that and remerge the package, the binary in /usr/bin gets deleted and not installed again. Then, when I want to unmerge it I get: Couldn't find any matching installed packages. During the merging: <<< obj /usr/bin/xlock --- !empty dir /usr/bin <<< obj /usr/X11R6/lib/X11/app-defaults/XLock And later: >>> original instance of package unmerged safely. Kinda strange. That ebuilds needs some work, but I'm not experienced enough to do it myself :(