On Wed, Sep 15, 2004, Dennis McRitchie wrote: > When emacs-21.3-2.1.0.src.rpm builds, it *implicitly* looks for xaw3d and > uses it if it finds it. However, since there is no explicit dependency on > xaw3d, openpkg-tools may choose to build emacs first. In this case, the > build will succeed but xaw3d will not be included, and the scroll bars will > not work as expected. > > One solution is to add a "with_xaw3d" option to the emacs spec file to force > an RPM requirement for xaw3d, and thus guarantee that the latter will be > built first by openpkg-tools.
Certainly a nasty side-effect. There are just two problems here: 1. "emacs" is a BASE class package and "xaw3d" just of class PLUS. Hence we cannot simply add a dependency of "xaw3d" to "emacs". 2. That software picks up whatever it finds staying around on the system is a general problem. To some extend it can be workarounded, but in general it is not solvable through (RPM) packaging. The order to package installations are not arbitrary if one wants exactly the same results. Yes, I know that this is nasty and one would expect it differently, but up to now really everyone doing packaging is confronted with this problem. The only solution would be to build a package in a dedicated (everytime) from-scratch established environment where really just the explicit dependencies are installed. Hmmm... this is possible but unusable. So, we can only workaround this here by adding the "with_xaw3d" option to "emacs" (ignoring that it is a BASE/PLUS conflict) _AND_ forcing "emacs" to ignore (by tricking config.cache, etc) an existing xaw3d if the option is NOT enabled. Now done in OpenPKG-CURRENT with emacs-21.3-20040916 or higher. See http://cvs.openpkg.org/chngview?cn=19028 for details. Thanks for the hint. Yours, Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
