illumos gate

Why?

1. ldd /usr/sbin/beadm
   libnvpair.so.1 => /lib/libnvpair.so.1
   libbe.so.1 => /usr/lib/libbe.so.1
   libc.so.1 => /lib/libc.so.1
   libnsl.so.1 => /lib/libnsl.so.1
   libzfs.so.1 => /lib/libzfs.so.1
   libinstzones.so.1 => /usr/lib/libinstzones.so.1
   libuuid.so.1 => /lib/libuuid.so.1
   libgen.so.1 => /lib/libgen.so.1
   libdevinfo.so.1 => /lib/libdevinfo.so.1
   libmp.so.2 => /lib/libmp.so.2
   libmd.so.1 => /lib/libmd.so.1
   libm.so.2 => /lib/libm.so.2
   libdevid.so.1 => /lib/libdevid.so.1
   libuutil.so.1 => /lib/libuutil.so.1
   libavl.so.1 => /lib/libavl.so.1
   libefi.so.1 => /lib/libefi.so.1
   libadm.so.1 => /lib/libadm.so.1
   libidmap.so.1 => /usr/lib/libidmap.so.1
   libtsol.so.2 => /lib/libtsol.so.2
   libumem.so.1 => /lib/libumem.so.1
   libcontract.so.1 => /lib/libcontract.so.1
   libzonecfg.so.1 => /usr/lib/libzonecfg.so.1
   libsocket.so.1 => /lib/libsocket.so.1
   libdlpi.so.1 => /lib/libdlpi.so.1
   libsec.so.1 => /lib/libsec.so.1
   libsecdb.so.1 => /lib/libsecdb.so.1
   libsysevent.so.1 => /lib/libsysevent.so.1
   libbrand.so.1 => /usr/lib/libbrand.so.1
   libpool.so.1 => /usr/lib/libpool.so.1
   libscf.so.1 => /lib/libscf.so.1
   libproc.so.1 => /lib/libproc.so.1
   libbsm.so.1 => /lib/libbsm.so.1
   libxml2.so.2 => /lib/libxml2.so.2
   libinetutil.so.1 => /lib/libinetutil.so.1
   libdladm.so.1 => /lib/libdladm.so.1
   libexacct.so.1 => /usr/lib/libexacct.so.1
   libsmbios.so.1 => /usr/lib/libsmbios.so.1
   librtld_db.so.1 => /lib/librtld_db.so.1
   libelf.so.1 => /lib/libelf.so.1
   libctf.so.1 => /lib/libctf.so.1
   libpthread.so.1 => /lib/libpthread.so.1
   libz.so.1 => /lib/libz.so.1
   librcm.so.1 => /lib/librcm.so.1
   libkstat.so.1 => /lib/libkstat.so.1
   libcurses.so.1 => /lib/libcurses.so.1

1. pkg search /usr/lib/libinstzones.so.1
   INDEX ACTION VALUE PACKAGE
   path file usr/lib/libinstzones.so.1 pkg:/package/svr4@0.5.11-0.151.1

I'm working on generation DEB packages based on manifests info and will be better to have all dependencies for packages in manifest.mf file.

If you're using the package dependencies from the IPS manifests to define the dependencies in other manifests, you want to use the manifests after the IPS pkgdepend has run, and discovered all of the automatic dependencies.

it will be working on system based on IPS.
If I have system based on DPKG + APT - I couldn't correct identify dependencies by pkgdepend.
I know how to identify dependencies in installed system, but I don't know how to check dependencies for non-installed yet packages.

will be better to have basic dependencies in manifest.mf - from illumos-gate stuff, not system.

As I have noticed 9 years later, it looks like the actual bug here is that libinstzones is for some weird reason shipped in package/svr4, while its symlinks (only) are shipped in system/library/install/libinstzones -- install/beadm doesn't need to depend on package/svr4, really.