On Sun, 2009-04-26 at 12:20 -0500, Rex Dieter wrote:
On 04/26/2009 11:59 AM, Eli Wapniarski wrote:
> Its a packaging error because the package is not required to make marble
> work. If digikam it is not required it is not a dependency. An error In
> computer parlance is called a bug.
It's the other way around, and it's not a packaging bug.
digikam requires kdeedu-marble, if built with marble support.
install both and try
rpm -e --nodeps kdeedu-marble
digikam will no longer start.
Which is kind of where we came in. Once more with feeling: there's no
user-level reason for digikam to require marble if the user doesn't need
marble's features. I'm guessing that the first versions of digikam
didn't have this dependancy, but someone thought that geo-tagging would
be a cool feature and just created the dependancy without considering
what proportion of users would really use it. That's OK if a feature is
cheap, but marble is not cheap, it's a huge package on its own. In fact
it's actually larger than digikam itself!
If digikam is configured in such a way that this requirement exists even
if the user doesn't ask for it, then IMHO that's something the digikam
maintainers should consider changing.