[Kde-imaging] [Bug 149666] [PATCH] iPod Export kipi plugin cannot be disabled at compile time when libgpod is present on system
MatÄj Laitl
strohel at gmail.com
Wed Sep 26 17:42:41 CEST 2007
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=149666
------- Additional Comments From strohel gmail com 2007-09-26 17:42 -------
In reply to comment #4:
While current behaviour is perfectly OK for binary based distros, individual developers and enthusiasts, it is huge pita for source based distros, such as Gentoo.
Let me explain:
In source distros, user usually control what features will be enabled or disabled in particular package by some distro-specific way, resulting in --with-feature or --without-feature being automatically passed to package's ./configure. However, this is used also to mark actual dependencies of a package, for example, if she opts to enable ipod support in kipi-plugins, they will have dynamic dependency on libgpod.
Assume following scenario:
1. Uses installs Amarok with ipod feature enabled, which in turn pulls libgpod as a dependency.
2. She installs kipi-plugins _without_ ipod feature enabled, because she is not interested in transferring photos to iPod. (thus no libgpod dependency is recorded to kipi-plugins)
3. She uninstalls Amarok, which in turn uninstalls libgpod, because distro's package manager thinks that it is no longer needed by any package.
4. User's kipi-plugins break, because library they linked against, libgpod, is no longer present on the system.
Step 4 happens because distro's package manager was not able to disable ipod support in kipi-plugins. My patch solves it.
This is one of many scenarios when such breakage can happen. Among possible solutions, patching package's build system is far the best. Please see already posted http://www.gentoo.org/proj/en/qa/automagic.xml for details.
Regards,
Matěj
More information about the Kde-imaging
mailing list