https://bugzilla.novell.com/show_bug.cgi?id=223524 ------- Comment #9 from eich@novell.com 2006-11-24 10:31 MST ------- I see problems with fonts, app-defaults shared libraries, man pages and binaries. Problems may also exist when building packages if static libs or include files are searched for in /usr/X11R6. I don't really think the latter issue is really relevant - sane packages using the imake or pkgconfig data should be save. Others need to be fixed - but since the sources are available this shouldn't be a problem. fonts: fonts are searched by fontconfig and xserver. both have configurable search paths. Problems arise when third party apps try to install fonts in /usr/X11R6 or /usr/X11. We can 'fix' this by keeping the /usr/X11R6 environment (including the symlink from /usr/X11 to /usr/X11R6/ around for legacy apps. app defaults: I'm currently trying to understand how the loading mechanism works. There seem to be some inconsitencies in the way it is configured with autotools if I understand the loading mechansim right. In any case that only matters for Xt applications (native, Xaw and Motif) only. app-defaults are an Xt feature - not Xlib. Legacy apps could continue to install their stuff into the old directories if we can set the search path right. From what I see from the code it would require a minor patch to libXt/configure.ac. However this stuff is rather confusing. As it currently looks like Xt uses a search path for all sorts of files including app-defaults. If this is really the case we should add /usr/X11R6/lib/X11 there. Binaries: Bigger problem! Creating a symlink from /usr/bin/X11 to /usr/bin is easy. But how do we handle /usr/X11R6/bin? We cannot link it to /usr/bin as it may not be empty. If we keep it around we would have to add it to the search path. However there may still be tons of scripts looking for xterm and the servers in there which is probably Harald's biggest concern. We could solve this to some extent by symlinking 'strategic' binaries (the servers and xterm) there. man pages: legacy apps may want to dump man pages to /usr/X11R6/man. This needs to be kept in the man search path. This is the case on 10.2. shared libs: legacy apps may dump their shared libs in /usr/X11R6/lib/. We therefore need to keep this directory in the ldconfig search path. This is already the case on 10.2. Do we need to set the module search path to /usr/X11R6/lib/modules for 3rd party drivers? This is not uncritical because of parallel 32 and 64 bit installs. I will continue to investigate the load path issue with /usr/X11R6/lib/X11. Have I missed anything? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.