On 12/14/06, Artem Kachitchkine <Artem.Kachitchkin at sun.com> wrote:
>
>
> > solution isn't to put libfsmgt into a separate package, it's to move it
> > into SUNWcsl. (Hopefully this is what fixing bugid 6496726 will do.)
>
> Not for every case, but some dependencies can be relaxed by making
> programs
> dlopen() optional libraries. If such library is not installed, the program
> would
> report that the corresponding feature is not available, without affecting
> other
> features.
>
> That is a first step.
Though the second step would be (for now with the tools we have) to *NOT*
list the other packages in the 'depend' file.
I've searched through a few of these cases recently. Many things are already
dlopen'd. I beleive that the connection to X11 in Java is only done if the
java app casues the JVM to dlopn libAWT.so. I unpacked the files in
SUNWxwsvr so I could run them through ldd to see if they actually directly
used any libs from SUNWgnome-a11y-libs. I found no direct links, and so I'm
ignoring that dependency for now. (I haven't run the screensave yet.) I've
done the same to other packages looking for direct links to the evolution
libs they claim to depend on. I may not be checking in the most complete
way, and even if the use dlopen, the programs may not handle the missing
libraries in the most graceful way.
But there has to be something better.
I wrote a little script to expand the packages pulled in by a single
package. Here's what it gives for SUNWxwsvr (Xscreensaver)
(This tree is pruned so that each Pkg is only listed once.)
SUNWxwsvr
SUNWcsr
SUNWcsu
SUNWcsl
SUNWgnome-base-libs
SUNWcar
SUNWkvm
SUNWcsd
SUNWgnome-base-libs-root
SUNWpostrun-root
SUNWxwxft
SUNWfreetype2
SUNWfontconfig
SUNWfontconfig-root
SUNWlexpt
SUNWcakr
SUNWckr
SUNWcnetr
SUNWlibpopt
SUNWpng
SUNWTiff
SUNWjpg
SUNWPython
SUNWopenssl-libraries
SUNWTk
SUNWTcl
SUNWgcmn
SUNWbzip
SUNWlibmsr
SUNWmlib
SUNWpostrun
SUNWperl584core
SUNWlibms
SUNWlxml
SUNWxwplt
SUNWesu
SUNWperl584usr
SUNWcpp
SUNWcslr
SUNWxwplr
SUNWxwfsw
SUNWxwrtl
SUNWzlib
SUNWgnome-config
SUNWgnome-config-root
SUNWgnome-component
SUNWgnome-component-root
SUNWgnome-a11y-libs
SUNWgnome-a11y-base-libs
SUNWgnome-libs
SUNWgnome-libs-root
SUNWgnome-vfs
SUNWgnome-vfs-root
SUNWdbus
SUNWdbus-root
SUNWPython-extra
SUNWsmbau
SUNWsmbar
SUNWhal
SUNWhwdata
SUNWhalr
SUNWpolkit
SUNWgnome-audio
SUNWlibexif
SUNWlxsl
SUNWgnome-panel
SUNWgnome-panel-root
SUNWevolution-data-server
SUNWtls
SUNWevolution-libs
SUNWgnome-print
SUNWgnome-print-root
SUNWscplp
SUNWpcr
SUNWpcu
SUNWpapi
SUNWlibgpg-error
SUNWpr
SUNWgnutls
SUNWlibgcrypt
SUNWkrbu
SUNWkrbr
SUNWgss
SUNWgssc
SUNWj5rt
SUNWmfrun
SUNWdtcor
SUNWctpls
SUNWlibC
SUNWzoner
SUNWzoneu
SUNWpool
SUNWpoolr
SUNWluu
SUNWadmfw
SUNWadmfr
SUNWadmc
SUNWmdu
SUNWmdr
SUNWlur
SUNWadmap
SUNWadmr
SUNWadmlib-sysid
SUNWlucfg
SUNWluzone
SUNWtecla
SUNWzfsu
SUNWzfsr
SUNWzfskr
SUNWsmapi
SUNWpkgcmdsu
SUNWpkgcmdsr
SUNWwbsup
SUNWwsr2
SUNWproduct-registry-root
SUNWxwice
SUNWxorg-clientlibs
There are 117 pkgs pulled in by SUNWxwsvr. Some of these are in SUNWCmreq,
but far too many are not.
Some are valid. Many are not.
I'm pretty sure there isn't a dependendcy link between Xscreensaver, and
ZFS? or Zones? or even Java for that matter.
I think there is more of a problem with what the developers have (or
haven't!) listed in the depend file than there really is with what libs
programs link to, etc.
Though I'm sure more could be done there too.
-Kyle
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/install-discuss/attachments/20061215/1228304c/attachment.html>
