Missing dependency in wpa_supplicant-dbus or dbus.tcz?

[ctor]

OS: corepure64 version 15

Until I manually loaded libcap.tcz, wpa_passphrase and wpa_supplicant were missing libcap.so.2 library. Also dbus-daemon in dbus.tcz extension needed libcap.so.2. Shouldn't libcap.tcz be added to dbus.tcz.dep?

[Rich]

Hi ctor
It should be there.
This is the  wpa_supplicant-dbus.tcz  tree file:

Code: [Select]

wpa_supplicant-dbus.tcz
   libnl.tcz
   dbus.tcz
      expat2.tcz
      elogind.tcz
         acl.tcz
            attr.tcz
         libcap.tcz
            attr.tcz
         util-linux.tcz
            readline.tcz
               ncursesw.tcz
            udev-lib.tcz
   openssl.tcz
   readline.tcz
      ncursesw.tcz
   wireless_tools.tcz
      wireless-6.6.8-tinycore64.tcz
      libiw.tczFound here:
http://tinycorelinux.net/15.x/x86_64/tcz/wpa_supplicant-dbus.tcz.tree
You can see  wpa_supplicant-dbus  depends on  dbus  depends on  elogind  depends on  libcap.

And this is list file for for  libcap:

Code: [Select]

/usr/local/lib/libcap.so
/usr/local/lib/libcap.so.2
/usr/local/lib/libcap.so.2.25
/usr/local/sbin/capsh
/usr/local/sbin/getcap
/usr/local/sbin/getpcaps
/usr/local/sbin/setcapFound here:
http://tinycorelinux.net/15.x/x86_64/tcz/libcap.tcz.list
Which shows it provides  libcap.so.2.

[yvs]

btw

Code: [Select]

$ mount | grep elogin
/mnt/sda1/tce/optional/elogind.tcz on /tmp/tcloop/elogind type squashfs (ro,relatime,errors=continue)

$ ldd /tmp/tcloop/elogind/usr/local/bin/busctl | grep -i 'not found'
        libpam.so.0 => not found

$ uname -sm
Linux x86_64

p.s. TC x86_64 and Linux caps in general:
Could you please share what's a reason to build extensions with binaries linked to libcap if squashfs module is built without xattr support? If I got it correctly, xattrs are needed to store linux caps.

[Rich]

Hi yvs
linux-pam.tcz  added to  15.x/x86_64/tcz/elogind.tcz.dep.
Thank you for reporting this.

[Juanito]

I don’t recall for this particular case, but there are certainly some packages where it is not possible to disable building against libcap.

[yvs]

I don’t recall for this particular case, but there are certainly some packages where it is not possible to disable building against libcap.

I'd suppose it's because to maintain some common way of extension building among architectures (linux caps are usable with xattrs that kept in extension on TC arm), but probably it's not a cause because many extensions are built differently and even named differently sometimes.