>Number:         12870
>Category:       pkg
>Synopsis:       Use of Xaw-Xpm in some new packages (e.g. kde2/koffice!) causes many older packages that wanted Xaw3d to be unbuildable/uninstallable.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 08 08:30:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        20010504
>Organization:
The NetBSD Project
>Environment:
System: NetBSD becasse.cs.stevens-tech.edu 1.5.1_ALPHA NetBSD 1.5.1_ALPHA (BOCK) #16: Wed Feb 28 16:55:59 EST 2001 root@amstel.cs.stevens-tech.edu:/usr/src/sys/arch/i386/compile/BOCK i386


>Description:
Some newer packages (e.g. the very-popular KDE2/koffice) have hardcoded
dependencies on a particular version of Xaw, in this case Xaw-Xpm.  This
causes two kinds of lossage:

1) If you have XAW_STYLE set to "3d", these packages can't be built without
   removing Xaw3d AND ANY PACKAGES LINKED TO IT, removing XAW_STYLE from
   mk.conf, and starting over.  This is not good.

2) If you've built and installed any of these packages, you can't build
   any packages that have hardcoded dependencies on Xaw3d, e.g. gv!  This
   is even worse, because there's a good bit of dependency fan-out from
   gv et al which, again, can cause more of pkgsrc to be broken than is
   immediately obvious.

>How-To-Repeat:
   Install koffice.  Then try to install gv.  Get ready to lose.
>Fix:
   It's ugly, but we probably need to change the shlib name for each of
   these nonstandard libXaw implementations so that it's unique.  This
   would mean whacking every package that wants the shlib to be called
   libXaw, but... what else could we do (perhaps convert all packages
   that use Xaw3d to use Xaw-Xpm?  This would significantly change their
   look-and-feel, AFAICT)?
>Release-Note:
>Audit-Trail:
>Unformatted: