Bug 1650 – xlockmore ebuild has got problems

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Cedric Meury 2002-04-10 10:23:42 UTC]

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 :(

[Comment 1 Cedric Meury 2002-04-10 14:07:52 UTC]

The thing about unmering had nothing to do with xlockmore, forget that, sorry
for any inconveniences.
But the --enable-xlockrc still is a problem.

[Comment 2 Cedric Meury 2002-04-10 15:20:34 UTC]

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.

[Comment 3 Seemant Kulleen (RETIRED) 2002-04-11 11:23:50 UTC]

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.

[Comment 4 Seemant Kulleen (RETIRED) 2002-04-13 22:57:14 UTC]

OK, I have added a test to the ebuild -- if "pam" is not in your USE string,
then it will enable xlockrc instead.