=?UTF-8?Q?J=C3=B6rg-Volker?= Peetz writes... > Package: pciutils > Version: 1:2.2.4~pre4-1 > > This Package claims to depend on package libpci2. The executables it > contains are > > /usr/bin/lspci > /usr/bin/setpci > /usr/bin/update-pciids > /usr/bin/pcimodules > > But none of them show a dependency on libpci2, when inspected with ldd. > So why the dependency on libpci2?
The dependency is needed while we transition from having libpci as a shared library to as an archive library. There may be packages that have a dependency on pciutils because of a need for the shared library. In the long term those applications should switch to building statically, in the short term they can depend on the new libpci2 package directly. But until all applications have moved to doing one of those two things, we have created the dependency you mention so that things will keep working. We have to keep in mind not only packages in Debian, but end user and 3rd party software as well. Post etch and once all the packages in Debian have transitioned we will drop the dependency and any end user or third party stuff still relying on that will break and need to be updated. OK? -- Matt Taggart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
