Bug 11933 - XEmacs ebuild should include /usr/lib/xemacs/mule-packages as argument to pkg-path if the mule USE variable is in effect.
|
Bug#:
11933
|
Product: Gentoo Linux
|
Version: 1.4_rc1
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: DUPLICATE
|
Assigned To: rendhalver@gentoo.org
|
Reported By: zhenya@freeshell.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: XEmacs ebuild should include /usr/lib/xemacs/mule-packages as argument to pkg-path if the mule USE variable is in effect.
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2002-12-10 19:04 0000
|
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) [details]
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 ***