On 11/21/2012 01:28 PM, David Faure wrote:
Second issue (and proposal): where should go the kwalletdefaultplugin?
This plugin actually contains the old KWallet API implementation, the
one which calls the kwalletd.
I think the best place for kwalletdefaultplugin should be
kde-runtime/kwalletd. Th
On Wednesday 21 November 2012 13:28:28 David Faure wrote:
> Beep, incompatibility here. The type "functional" means "it's only a
> library". Plugins are runtime dependencies, so this is an "integration"
> framework (confirmed by the fact that it aims at integrating with the OS
> wallet service). Bu
Hello Valentin,
Sorry for the delayed reply, too many conferences this month ;)
On Sunday 04 November 2012 16:03:12 Valentin Rusu wrote:
> Hello,
>
> Now that I'm using a plug-in version of the KWallet API on my system, I
> think it would be the time to put it at the right place inside the
> fra
On 11/05/2012 04:49 PM, Jon Severinsson wrote:
söndagen den 4 november 2012 16:03:12 skrev Valentin Rusu:
This plugin actually contains the old KWallet API implementation, the
one which calls the kwalletd.
I think the best place for kwalletdefaultplugin should be
kde-runtime/kwalletd. This way,
söndagen den 4 november 2012 16:03:12 skrev Valentin Rusu:
> This plugin actually contains the old KWallet API implementation, the
> one which calls the kwalletd.
> I think the best place for kwalletdefaultplugin should be
> kde-runtime/kwalletd. This way, this plugin will get installed at the
> s
Hello,
Now that I'm using a plug-in version of the KWallet API on my system, I
think it would be the time to put it at the right place inside the
frameworks branch, if you don't mind.
The logic actually lives inside kdelibs/ksecretsservice branch and,
despite that branch's name, the only cha
