[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:       "MatÄj" Laitl <strohel () gmail ! com>
Date:       2007-09-30 15:07:21
Message-ID: 20070930150721.13628.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 strohel gmail com  2007-09-30 17:07 -------
> Ok I see your point (comment #5) but leaving the user decide if enabling or not an \
> option, in the case of plugins, should mean --with/without-feature with feature \
> (IMO) equal to the plugin itself, not the libgpod to avoid compiling it. Is it ok \
> for you?

Okay, you decide, the name not really important.

> Gilles can we do something like that, i mean allow disabling all the plugins?

If you let me comment on that, I don't think it's worth the effort. I think it's \
worth only for optional plugins, that have external dependency. (in which case it \
would be more reasonable to name --with{,out}-stuff after a dependency and not after \
                the feature.
Example: --without-libtiff    build kipi-plugins without Acquire Images, RAW \
Converter and JPEG Lossless plugins. (default=check) and not three separate options \
to effectively disable linking against libtiff)

If you want, I can try to write a patch for you. (dealing with all optional external \
dependencies)

Thanks for your effort,
    Matěj


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