http://bugzilla.wpkg.org/show_bug.cgi?id=117 --- Comment #15 from Tomasz Chmielewski <mangoo at wpkg.org> 2008-05-11 12:57:41 --- >> You are welcome not to, of course. But this is what Debian calls dependency >> management and it seems to work for them. > > I am using only one single Debian system and up to now I never looked at such > details. But for Debian package management it might be slightly different. Unless I'm missing something, WPKG dependencies have the same logic as Debian's package management (.deb packages): samba_3.0.28a-2_i386.deb / INFO: (...) Depends: adduser, debconf (>= 0.5) | debconf-2.0, libacl1 (>= 2.2.11-1), libattr1 (>= 2.4.41-1), libc6 (>= 2.7-1), libcomerr2 (>= 1.33-3), libcupsys2 (>= 1.3.4), libgnutls26 (>= 2.2.0-0), libkrb53 (>= 1.6.dfsg.2), libldap-2.4-2 (>= 2.4.7), libpam-modules, libpam-runtime (>= 0.76-13.1), libpam0g (>= 0.99.7.1), libpopt0 (>= 1.10), logrotate, lsb-base (>= 3.0-6), procps, samba-common (= 1:3.0.28a-2), update-inetd, zlib1g Or other distros using .rpm packages: samba-server-3.0.28a-2mdv2008.1.i586.rpm / INFO/REQUIRENAME: samba-common = 3.0.28a rpm-helper /bin/sh /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 bash libacl.so.1 libattr.so.1 libc.so.6 (...) Here, as well, dependencies (requires) are installed first, which is the same as WPKG does now. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |