this leads to removing digikam as well.
What has a mapping application go to do with a photo

manager?
Digikam can show where a photo was taken on a map if
the EXIF tags are there. It should probably be an
optional dependency, but that'd be something for
upstream to sort out most likely.
- --Ben

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Patrick O'Callaghan wrote:
> I want to remove kdeedu-marble, having no use for it,
but yum tells me
> this leads to removing digikam as well.
>
> What has a mapping application go to do with a photo
manager?
Digikam can show where a photo was taken on a map if
the EXIF tags are there. It should probably be an
optional dependency, but that'd be something for
upstream to sort out most likely.

correct, GEOIP tagging feature, which is linked into the application, so
it's not possible to remove the hard dep (without losing the feature).
-- Rex

Ben Boeckel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Patrick O'Callaghan wrote:
>
>> I want to remove kdeedu-marble, having no use for it,
> but yum tells me
>> this leads to removing digikam as well.
>>
>> What has a mapping application go to do with a photo
> manager?
>
> Digikam can show where a photo was taken on a map if
> the EXIF tags are there. It should probably be an
> optional dependency, but that'd be something for
> upstream to sort out most likely.
correct, GEOIP tagging feature, which is linked into the application, so
it's not possible to remove the hard dep (without losing the feature).

<rant>
Let me just say for the record that this sucks. kdeedu-marble is a 30MB
download which I have no intention of using, not even for geo-tagging,
i.e. I don't care about losing the feature and I conjecture that this is
likely to be true of a great many users. It's absurd that this isn't
optional. I get it that it's an upstream problem, so my complaint is
really directed at the KDE folks, but still.
</rant>
I guess I'll register my displeasure on the KDE BZ.
poc

really directed at the KDE folks, but still.
</rant>
I guess I'll register my displeasure on the KDE BZ.
poc

It could possibly be added as a KService, but I don't
know if Digikam's architecture is amenable to this
(plugins would handle displaying of certain EXIF
tags?). If it can't be made into a KService, there's
not much we can do about it. If it can be, I'd expect
4.4 to be the earliest you can expect it. Mind linking
the bug you filed here?
- --Ben

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Patrick O'Callaghan wrote:
> On 04/23/2009 08:35 AM, Rex Dieter wrote:
>> Ben Boeckel wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Patrick O'Callaghan wrote:
>>>
>>>> I want to remove kdeedu-marble, having no use for
it,
>>> but yum tells me
>>>> this leads to removing digikam as well.
>>>>
>>>> What has a mapping application go to do with a
photo
>>> manager?
>>>
>>> Digikam can show where a photo was taken on a map
if
>>> the EXIF tags are there. It should probably be an
>>> optional dependency, but that'd be something for
>>> upstream to sort out most likely.
>> correct, GEOIP tagging feature, which is linked into
the application, so
>> it's not possible to remove the hard dep (without
losing the feature).
> <rant>
> Let me just say for the record that this sucks.
kdeedu-marble is a 30MB
> download which I have no intention of using, not even
for geo-tagging,
> i.e. I don't care about losing the feature and I
conjecture that this is
> likely to be true of a great many users. It's absurd
that this isn't
> optional. I get it that it's an upstream problem, so
my complaint is
> really directed at the KDE folks, but still.
> </rant>
>
> I guess I'll register my displeasure on the KDE BZ.
>
> poc
It could possibly be added as a KService, but I don't
know if Digikam's architecture is amenable to this
(plugins would handle displaying of certain EXIF
tags?). If it can't be made into a KService, there's
not much we can do about it. If it can be, I'd expect
4.4 to be the earliest you can expect it. Mind linking
the bug you filed here?

Want me to close this as INVALID? ;-)
I don't see how the dependency is a bug at all, nor do I understand the
point of absolutely wanting to remove a package just to remove it. Disk
space is cheap.
Kevin Kofler

Patrick O'Callaghan wrote:
> https://bugs.kde.org/show_bug.cgi?id=190476
Want me to close this as INVALID? ;-)
I don't see how the dependency is a bug at all, nor do I understand the
point of absolutely wanting to remove a package just to remove it. Disk
space is cheap.

You're missing the point. I don't care about the disk space, but I do
care about having to download a 30MB package that I'm never going to use
over a slow DSL line, not only on first installation but also on
subsequent updates. I'm sure people on dialup feel even more strongly
about this.
poc

On Sun, 2009-04-26 at 05:32 +0200, Kevin Kofler wrote:
> Patrick O'Callaghan wrote:
> > https://bugs.kde.org/show_bug.cgi?id=190476
>
> Want me to close this as INVALID? ;-)
>
> I don't see how the dependency is a bug at all, nor do I understand the
> point of absolutely wanting to remove a package just to remove it. Disk
> space is cheap.

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.

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.
-- Rex

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.
poc

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.

Ahh. So the feature is compiled in. As such digikam expects marble to be in place. Then
Patrick I would have to agree that it be included. With all due respect; for those that
would be relying on the feature it would be sorely missed if it wasn't there. And then
we would be complaining that the feature wasn't included.
Maybe you should try to communicate with the developers and ask them if there is any way
to get digikam to compile with support built, check if the package is installed and run
even if the package is not installed. That way the dependency can be removed. Until such
time Fedora has no real option but to include it.
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

On Sunday 26 April 2009 20:20:31 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.
>
Ahh. So the feature is compiled in. As such digikam expects marble to
be in place. Then Patrick I would have to agree that it be included.
With all due respect; for those that would be relying on the feature
it would be sorely missed if it wasn't there. And then we would be
complaining that the feature wasn't included.
Maybe you should try to communicate with the developers and ask them
if there is any way to get digikam to compile with support built,
check if the package is installed and run even if the package is not
installed. That way the dependency can be removed. Until such time
Fedora has no real option but to include it.

It's a 1Mbps line shared among 3 users (and 4 computers) in the
household. As long as nothing else is going on, that means around
115KBps effective dl speed, assuming the servers aren't overloaded.
I'd gladly pay for better b/w, but the ISP offers only two alternatives,
a 1.5Mbps service for about 60% higher cost, and a 2Mbps service for *4
times* the cost of 1Mpbs (yes, you read that correctly, the cost rises
exponentially, contrary to what you see almost anywhere else in the
world). Other ISPs claim better speed, but the scuttlebutt is that this
should be taken with a pinch of salt.
Anyway, this is all somewhat tangential. I don't want to give the
impression that the marble issue is so burdensome as to seriously affect
me. I just don't like unnecessary bloat, and I wouldn't like it even if
I had 10Mbps or 100Mpbs.
poc