[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 149666] [PATCH] iPod Export kipi plugin cannot be disabled at
From:       Angelo Naselli <anaselli () linux ! it>
Date:       2007-09-30 15:58:23
Message-ID: 20070930155823.18684.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=149666         




------- Additional Comments From anaselli linux it  2007-09-30 17:58 -------
Matěj your help is more than welcome of course, but before starting let's see
another point of view. 
We're talking about plugins and even if i can see the external lib dependency
point, i can't get why for user should be easier removing a lib dependency instead of \
a plugin. I mean you talked about ipod-export and said that user can think he/she \
doesn't need it, so he/she should disable libgpod (in your example), that sonunds odd \
to me, i would disable the plugin instead.

OTOH you could be right in the case, as it happened, kipi-plugins has been released \
with libgpod X dependency, but stable system has libgpod X-1, in such a case \
--without-libgpod is right, but --without-ipodexport either. 

WDYT?


[prev in list] [next in list] [prev in thread] [next in thread]