This one time, at band camp, Bill Bennett wrote: >I'm gunshy of using other than rpm to install an application, >so I went searching for an elvis.rpm---found it at the elvis/pub >site and ftp'd it: > >elvis-2.2f-3.i686.rpm
Does the site tell you how they built that RPM? After reading your description, I wonder if the installed version just doesn't split out libtinfo; your installed version is two minor versions above the one you tried to install. If that's the case, then it might be that the elvis RPM was built against old libraries and thus the deps may be out of date. If you force install elvis it might just work anyway. rpm -Uvh --nodeps elvis.rpm If, however, elvis doesn't work after this, then my guess is wrong and libtinfo isn't sucked into the rest of ncurses. (A little thought further makes me think this won't work anyway because the dynamic loader will try to find libtinfo anyway, as it'll be listed in the elvis binary's required library list, and fail.) If you can work out what elvis.rpm was built on, then you can probably find out why the RPM needs libtinfo; perhaps it's built for a different RPM based distro. You could always try getting the src.rpm or tarball and building the RPM yourself. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
