Pete Ware <ware(a)cis.ohio-state.edu&gt; writes: But in case of RPM package (without a superduper-(notrunning)-GNOME-rpm frontend) the user has the problem to find the package he needs if the requires of an other package only list 'internal' names. Example: xemacs-base provides (add-log advice annotations assoc case-table chistory comint-xemacs comint compile debug ebuff-menu echistory edmacro ehelp electric enriched env facemenu ffap helper imenu iso-syntax macros novice outline overlay passwd pp regi ring shell skeleton sort thing time-stamp timezone xbm-button xpm-button) if there is now the dummy package which requires echistory, and the user has xemacs-base *not* installed (only and example!), rpm would say: dummy: could not be installed. package requires echistory Now the first thing a user looks for is a package named echistory-x.x-x.noarch.rpm, but he will find non, cause echistory is provided by xemacs-base-x.x-x.noarch.rpm. I want to solve this by only (or perhaps in addition) provide and require only *package names*. I hope this makes the topic a bit clearer. Regards, Oliver.