add -r misbehaves if you create another arch/foo while a locker is added

[geofft]

lunatique:~ geofft$ ls arch
common  i386_deb31  i386_deb40  i386_rhel4  scripts  sun4x_510
lunatique:~ geofft$ add geofft
lunatique:~ geofft$ mkdir -p arch/i386_deb50/bin
lunatique:~ geofft$ add -r geofft
lunatique:~ geofft$ add
/usr/local/bin:/usr/bin:/bin:/usr/games:{add windowmanagers*}:{add alpine*}:{add consult*}:{add git*}:{add nelhage*}:{add ops*}:{add outland*}:{add scripts*}:{add sipb*}:{add svn*}:{add alpine}:{add consult*}:{add sipb*}:{add svn}:{add geofft*}

In short, add tries to remove /mit/geofft/arch/i386_deb50/bin from my path, instead of the /mit/geofft/arch/i386_deb40/bin that is actually in my path.

[jdreed]

I think this falls under "Don't do that", but I'll keep it around in case we decide we care.

[jdreed]

Yeah, I'm tempted to WONTFIX this. I suppose one solution is for add to attempt to remove something from the path, and if it doesn't find it, then list all athdir paths for the locker, and attempt to remove those. That's... kind of inefficient, but would work.

[jdreed]

Fixed in the new liblocker, which hasn't been released yet.