Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
When the user specified that he/she wants to build a mule-ified XEmacs (by setting the "mule" USE option), then the package-path argument to configure should include /usr/lib/xemacs/mule-packages. If this isn't done various bad thing happen. Some examples of bad things are that XEmacs own package manager thinks that the mule-base package is not installed and that XEmacs cannot use any of the quail input methods. I'll attach a suggested patch.
Created an attachment (id=6388) [edit] Suggested patch: add /usr/lib/xemacs/mule-packages to --package-path if the mule USE option is set Suggested patch: add /usr/lib/xemacs/mule-packages to --package-path if the mule USE option is set
package-path is a bad way to do this package-path is used to specify a packages root the various xemacs|mule|site-packages live under that path the current ebuild sets --package-path=/usr/lib/xemacs/xemacs-packages/ this will ensure mule-packages are not found i have a couple of updated xemacs ebuilds that should be in portage shortly they will fix this problem
*** This bug has been marked as a duplicate of 11628 ***