Re: [Nepomuk] NAO::Symbols and ResourceWatcher

2012-05-03 Thread Sebastian Trüg
On 05/01/2012 02:11 PM, David Narvaez wrote: > On Mon, Apr 30, 2012 at 7:05 AM, Sebastian Trüg wrote: >> If there is still code not going through the Nepomuk frontend it must be >> treated as a bug. All data manipulation has to go through >> Nepomuk::Resource or the Nepomuk datamanagement API (add

Re: [Nepomuk] The Nepomuk Situation

2012-05-03 Thread Sebastian Trüg
nepomuk-core depends on kdelibs. So kdelibs cannot depend on nepomuk-core. We would have to get rid of those dependencies in kdelibs. But that should not be too hard. On 05/03/2012 11:21 AM, Vishesh Handa wrote: > I just noticed that this discussion is no longer cced to kcd. > > On Thu, May 3, 20

Re: [Nepomuk] The Nepomuk Situation

2012-05-03 Thread Vishesh Handa
I just noticed that this discussion is no longer cced to kcd. On Thu, May 3, 2012 at 2:47 PM, Christian Mollekopf wrote: > > > On Thu, May 3, 2012, at 02:22 PM, Vishesh Handa wrote: > > > > On Thu, May 3, 2012 at 3:09 AM, Christian Mollekopf > wrote: > > > On Thursday 03 May 2012 00.32:37 Vish

Re: [Nepomuk] The Nepomuk Situation

2012-05-03 Thread Christian Mollekopf
On Thu, May 3, 2012, at 02:22 PM, Vishesh Handa wrote: On Thu, May 3, 2012 at 3:09 AM, Christian Mollekopf <[1]chrig...@fastmail.fm> wrote: > On Thursday 03 May 2012 00.32:37 Vishesh Handa wrote: > > Hey everyone! > Hey Vishesh, Hey Christian Glad your tackling this, it's indeed a

Re: [Nepomuk] The Nepomuk Situation

2012-05-03 Thread Vishesh Handa
On Thu, May 3, 2012 at 3:09 AM, Christian Mollekopf wrote: > > On Thursday 03 May 2012 00.32:37 Vishesh Handa wrote: > > > > Hey everyone! > > > Hey Vishesh, > Hey Christian > > Glad your tackling this, it's indeed a rather painful situation. > > > > > So, we need a solution. > > > > The first s

Re: [Nepomuk] The Nepomuk Situation

2012-05-03 Thread Sebastian Trüg
On 05/02/2012 11:39 PM, Christian Mollekopf wrote: >> On Thursday 03 May 2012 00.32:37 Vishesh Handa wrote: >> >> Hey everyone! >> > Hey Vishesh, > > Glad your tackling this, it's indeed a rather painful situation. > >> >> So, we need a solution. >> >> The first solution - >> * Remove nepomuk fro