Off-Topic > Release Candidate Testing

microcore_v2.10rc1

<< < (2/4) > >>

Juanito:
Are we looking to have recursive deps load extensions in the order listed in the dep file as per "standard" deps?

If we assume for a moment that the avahi or dbus extensions try to start the dbus daemon from the start-up script (they no longer do this, but just for the sake of an example) and load rhythmbox using a recursive dep file, then the load order is:

avahi
dbus
expat2

..which means it wouldn't work.


--- Code: ---$ cat rhythmbox.dep
totem-pl-parser.tcz
gnome-media.tcz
libsoup-gnome.tcz
gst-plugins-good.tcz
gst-plugins-bad.tcz
gst-plugins-ugly.tcz
gst-python.tcz
gmime.tcz
pygtk.tcz
pyorbit.tcz
gnome-python.tcz
libnotify.tcz
libgpod.tcz
gnome-icon-theme.tcz
shared-mime-info.tcz

--- End code ---

bmarkus:
As far as I know startup scripts executed after all extensions are loaded in alphabetic order. Maybe I'm wrong...

Juanito:
Here's what I see when testing:
--- Code: ---$ tce-load -i /mnt/sda1/tmp/rhythmbox_rec/rhythmbox.tcz
shared-mime-info.tcz OK.
gnome-icon-theme.tcz OK.
libgpod.tcz OK.
libnotify.tcz OK.
popt.tcz OK.
libbonobo.tcz OK.
audiofile.tcz OK.
esound.tcz OK.
gamin.tcz OK.
udevadm.tcz OK.
libusb.tcz OK.
usb-utils.tcz OK.
libpci.tcz OK.
pci-utils.tcz OK.
hal.tcz OK.
nss-mdns.tcz OK.
libdaemon.tcz OK.
gcc_libs.tcz OK.
/usr/local/tce.installed/avahi: line 14: dbus-daemon: not found
avahi-daemon: error while loading shared libraries: libexpat.so.1: cannot open shared object file: No such file or directory
avahi.tcz OK.
gnome-vfs.tcz OK.
...
dbus.tcz OK.
...
expat2.tcz OK.
...
rhythmbox.tcz OK.
--- End code ---

again, I modified avahi to attempt to start dbus for the sake of testing

roberts:
I would be happy to look at a tarball of your test case, perhaps if posted bmarkus and myself could look at it. However avahi should not be a dependency of rythmbox. Look at Debian, avahi is a recommends. Additionally startup scripts should be for extensions and not embedded within the dependency chain. The dependecny chain is recusred in order load all reuired files needed by the requested extension. The requested extension is always loaded last, and therefore its startup script should be successful.

roberts:
To explain more look at:
http://packages.debian.org/sid/rhythmbox
and
http://packages.debian.org/sid/avahi-daemon
It would seem therefore they are separate and both would require a dependency chain that would be necessary, (and which happens to have many dependencies in common), for their startup script to be successful.

I would need to see a tarball(s) in order to more fully understand what is being attempted.

Navigation

[0] Message Index

[#] Next page

[*] Previous page