On Sat, 20 Apr 2002, Nicholas Robbins wrote:
> The following 31 packages will be installed or updated:
> app-defaults audiofile dlcompat esound freeciv freetype2 fvwm-common
> fvwm2-no-gnome gdbm gdk-pixbuf ghostscript-fonts gimp gnome-libs gtk+ gv
> hyperref libpng libstroke libtiff libxml2 netpbm pdftex pwm readline
> tetex-base transfig x-ghostscript-fonts xchat xemacs-sumo-pkg xfree86-base
> zlib
>
> The following 45 additional packages will be installed:
> aalib aalib-bin aalib-shlibs audiofile-bin audiofile-shlibs bonobo
> control-center db3 db3-shlibs esound-bin esound-common esound-shlibs expat
> freetype2-shlibs gal19 gal19-shlibs gconf gdbm-shlibs gdk-pixbuf-shlibs
> glibwww gmp gmp-shlibs gnome-core gnome-print gnome-vfs gtkhtml guile
> libglade libmpeg libmpeg-shlibs libpng-shlibs libstroke-shlibs libtiff-bin
> libtiff-shlibs libxml manconf netpbm-bin netpbm-shlibs oaf popt python
> readline-shlibs scrollkeeper tcltk xfontpath
> Do you want to continue? [Y/n]n
>
> That seems like a lot of 'additional packages' to me.
It's common for a sparse, young Fink installation to hit huge dependency
lists like this, just because your system doesn't have a lot of the basic
libraries that many other packages depend on. At a glance, esound, gimp,
xemacs, and xfree86 all have long lists of dependencies, as I recall. Also
note all the -bin, -shlibs, and -common packages: many of these are just
branches of one package that include executable (".exe") and shared
library (".dll") components; note as well that some of these are split
offs from packages being updated (libstroke <-> libstroke-shlibs), so
again you're kind of seeing duplication there.
> What's going on? Are some of the new packages just old packages being
> broken up into -shlibs and -bin subpackages? For example are "gnome-core
> gnome-print gnome-vfs" all just "gnome-libs" ?
Most of the gnome- ones look like truly separate components, but mostly,
yeah it is exactly as you're guessing. In most cases, I think these should
generally just compile once (which is good, as that's the slow step), then
produce several .deb archives that'll be installed separately. That's not
that bad though, maybe 30 seconds each or something [at least, based on
impressions from my 233/g3 iMac].
> Also I only see an xfree86-base update and nothing to
> indicate the new rootless server replacing my old rooted
> server. Will I have to do a
>
> fink remove xfree86-server
>
> and then
>
> fink install xfree86-rootless
>
> to get the new server?
In most cases -- not always, but usually -- the dpkg/apt system is smart
enough to remove any old components that need removing. Doing so manually
seems to be mainly a debugging technique for most usage.
--
Chris Devers [EMAIL PROTECTED]
Apache / mod_perl / http://homepage.mac.com/chdevers/resume/
"More war soon. You know how it is." -- mnftiu.cc
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
