[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: [Nepomuk] The Nepomuk Situation
From: Vishesh Handa <me () vhanda ! in>
Date: 2012-05-16 18:49:55
Message-ID: CAOPTMKAPHegQ5prV92cbBdEWeJ1F_nZcpTtnDgVtWrve9g1shg () mail ! gmail ! com
[Download RAW message or body]
On Thu, May 17, 2012 at 12:02 AM, Sebastian Trüg <trueg@kde.org> wrote:
> On 05/16/2012 08:23 PM, Vishesh Handa wrote:
> > What about kdelibs/nepomuk/utils/* and the other ui stuff?
> >
> > Or since those are just APIs they can wait.
>
> I say let's postpone them, they are still in kdelibs.
> The facets are quite weird and I am not sure about releasing them again.
> The ui stuff - not sure.
>
We have all the runtime stuff and nepomuk-core, that's all that matters
right now.
So, we just need to do -
1. use the Nepomuk2 namespace, and nepomuk2 include directory
2. Remove kde-runtime/nepomuk
Regarding 1, I like Ivan's suggestion about BEGIN_NEPOMUK_NAMESPACE. If you
want I can take care of it.
> > On Wed, May 16, 2012 at 11:49 PM, Sebastian Trüg <trueg@kde.org
> > <mailto:trueg@kde.org>> wrote:
> >
> > I now prepared the required repositories:
> >
> > scratch/trueg/nepomuk-kde-kio
> > contains the 3 Nepomuk kio slaves
> >
> > scratch/trueg/nepomuk-kde-config
> > contains the KCM and the controller systray app
> >
> > The question is: where should we move them? Something like
> "KDE/Base"?
> > I suppose questions like these have already been discussed with
> respect
> > to KDE5?
> >
> > Cheers,
> > Sebastian
> >
> > On 05/07/2012 03:58 PM, Sebastian Trüg wrote:
> > > On 05/07/2012 03:47 PM, ivan.cukic@gmail.com
> > <mailto:ivan.cukic@gmail.com> wrote:
> > >> Maybe there could be something like qt has -
> > BEGIN_NEPOMUK_NAMESPACE... So that if the same needs to be done in
> > the future, we could just change the macro value.
> > >
> > > That would be much more work since each cpp file has the
> namespaces in
> > > the method definitions.
> > >
> > >> I don't know, thinking that Nepomuk2 namespace is looking rather
> > ugly :)
> > >
> > > it is indeed.
> > >
> > >> The dirtiest solution library-wise would be to have everything in
> > NepomukCore::Nepomuk::Something so that the only change in the
> > current code of nepomuk users would be a using namespace NepomukCore;
> > >>
> > >> Sorry for being a bit vague, I'm writing from my phone.
> > >>
> > >> Cheerio,
> > >> IvanOn 7.5.12. 14.49 Vishesh Handa wrote:
> > >>
> > >>
> > >>
> > >> On Mon, May 7, 2012 at 6:13 PM, Sebastian Trüg <trueg@kde.org
> > <mailto:trueg@kde.org>> wrote:
> > >>
> > >> On 05/07/2012 02:35 PM, Vishesh Handa wrote:
> > >>>
> > >>>
> > >>> On Mon, May 7, 2012 at 5:54 PM, Sebastian Trüg <trueg@kde.org
> > <mailto:trueg@kde.org>
> > >>
> > >>> <mailto:trueg@kde.org <mailto:trueg@kde.org>>> wrote:
> > >>>
> > >>>
> > >>> On 05/07/2012 12:09 PM, Vishesh Handa wrote:
> > >>>
> > >>> > So, we're down to 3 options -
> > >>> >
> > >>> > *1.* nepomuk-core become a dependency of kdelibs. Kdelibs
> > is not
> > >>> touched.
> > >>> > *Problem:* Overlapping headers and possible mysterious
> > crashes if both
> > >>> > libraries are loaded.
> > >>> >
> > >>> > *2.* nepomuk-core installs headers under nepomuk2. It's
> > released
> > >>> > independently.
> > >>> > *Problem:* Mysterious crashes if both libraries are loaded.
> > >>> >
> > >>> > *3.* nepomuk-core installs headers under nepomuk2 and the
> > namespace is
> > >>> > changed to nepomuk2.
> > >>> > *Problem:* A lot more work :(
> > >>>
> > >>> Well, I suppose we could make this work with some sed magic.
> :P
> > >>> I would vote for option 3 which could then be reverted (or
> > not) for
> > >>> kde5.
> > >>>
> > >>>
> > >>> I would prefer option 2.
> > >>>
> > >>> The mysterious crashes would only happen if an application's
> plugin
> > >>> links to the incorrect libraries.
> > >>>
> > >>> Is that a possibility for us?
> > >>
> > >>
> > >> I already experienced that. Took me a while to find the reason.
> > >>
> > >>
> > >> Alright.
> > >>
> > >> I would like the Nepomuk2 namespace and include directories be
> > removed for the frameworks, but I guess it is not a big deal if that
> > doesn't happen.
> > >>
> > >> ----
> > >>
> > >> Okay, everyone. This is the point where you chime in and say -
> > "We're okay with this" or you raise your objections. We would like
> > to get this mess sorted in time for the 4.9 release.
> > >>
> > >>
> > >>
> > >>
> > > _______________________________________________
> > > Nepomuk mailing list
> > > Nepomuk@kde.org <mailto:Nepomuk@kde.org>
> > > https://mail.kde.org/mailman/listinfo/nepomuk
> > _______________________________________________
> > Nepomuk mailing list
> > Nepomuk@kde.org <mailto:Nepomuk@kde.org>
> > https://mail.kde.org/mailman/listinfo/nepomuk
> >
> >
> >
> >
> > --
> > Vishesh Handa
> >
>
--
Vishesh Handa
[Attachment #3 (text/html)]
<br><br><div class="gmail_quote">On Thu, May 17, 2012 at 12:02 AM, Sebastian Trüg \
<span dir="ltr"><<a href="mailto:trueg@kde.org" \
target="_blank">trueg@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <div class="im">On 05/16/2012 08:23 PM, Vishesh Handa \
wrote:<br> > What about kdelibs/nepomuk/utils/* and the other ui stuff?<br>
><br>
> Or since those are just APIs they can wait.<br>
<br>
</div>I say let's postpone them, they are still in kdelibs. \
</blockquote><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
The facets are quite weird and I am not sure about releasing them again.<br>
The ui stuff - not sure.<br></blockquote><div><br>We have all the runtime stuff and \
nepomuk-core, that's all that matters right now.<br><br>So, we just need to do \
-<br><br>1. use the Nepomuk2 namespace, and nepomuk2 include directory<br> 2. Remove \
kde-runtime/nepomuk<br><br>Regarding 1, I like Ivan's suggestion about \
BEGIN_NEPOMUK_NAMESPACE. If you want I can take care of it.<br><br></div><blockquote \
class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">
<div class="im"><br>
> On Wed, May 16, 2012 at 11:49 PM, Sebastian Trüg <<a \
href="mailto:trueg@kde.org">trueg@kde.org</a><br> </div><div class="im">> \
<mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>>> wrote:<br> \
><br> > I now prepared the required repositories:<br>
><br>
> scratch/trueg/nepomuk-kde-kio<br>
> contains the 3 Nepomuk kio slaves<br>
><br>
> scratch/trueg/nepomuk-kde-config<br>
> contains the KCM and the controller systray app<br>
><br>
> The question is: where should we move them? Something like \
"KDE/Base"?<br> > I suppose questions like these have already been \
discussed with respect<br> > to KDE5?<br>
><br>
> Cheers,<br>
> Sebastian<br>
><br>
> On 05/07/2012 03:58 PM, Sebastian Trüg wrote:<br>
> > On 05/07/2012 03:47 PM, <a \
href="mailto:ivan.cukic@gmail.com">ivan.cukic@gmail.com</a><br> </div><div \
class="im">> <mailto:<a \
href="mailto:ivan.cukic@gmail.com">ivan.cukic@gmail.com</a>> wrote:<br> > \
>> Maybe there could be something like qt has -<br> > \
BEGIN_NEPOMUK_NAMESPACE... So that if the same needs to be done in<br> > the \
future, we could just change the macro value.<br> > ><br>
> > That would be much more work since each cpp file has the namespaces \
in<br> > > the method definitions.<br>
> ><br>
> >> I don't know, thinking that Nepomuk2 namespace is looking \
rather<br> > ugly :)<br>
> ><br>
> > it is indeed.<br>
> ><br>
> >> The dirtiest solution library-wise would be to have everything \
in<br> > NepomukCore::Nepomuk::Something so that the only change in the<br>
> current code of nepomuk users would be a using namespace NepomukCore;<br>
> >><br>
> >> Sorry for being a bit vague, I'm writing from my phone.<br>
> >><br>
> >> Cheerio,<br>
> >> IvanOn 7.5.12. 14.49 Vishesh Handa wrote:<br>
> >><br>
> >><br>
> >><br>
> >> On Mon, May 7, 2012 at 6:13 PM, Sebastian Trüg <<a \
href="mailto:trueg@kde.org">trueg@kde.org</a><br> </div><div class="im">> \
<mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>>> wrote:<br> > \
>><br> > >> On 05/07/2012 02:35 PM, Vishesh Handa wrote:<br>
> >>><br>
> >>><br>
> >>> On Mon, May 7, 2012 at 5:54 PM, Sebastian Trüg <<a \
href="mailto:trueg@kde.org">trueg@kde.org</a><br> > <mailto:<a \
href="mailto:trueg@kde.org">trueg@kde.org</a>><br> > >><br>
</div><div><div class="h5">> >>> <mailto:<a \
href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a \
href="mailto:trueg@kde.org">trueg@kde.org</a>>>> wrote:<br> > \
>>><br> > >>><br>
> >>> On 05/07/2012 12:09 PM, Vishesh Handa wrote:<br>
> >>><br>
> >>> > So, we're down to 3 options -<br>
> >>> ><br>
> >>> > *1.* nepomuk-core become a dependency of kdelibs. \
Kdelibs<br> > is not<br>
> >>> touched.<br>
> >>> > *Problem:* Overlapping headers and possible \
mysterious<br> > crashes if both<br>
> >>> > libraries are loaded.<br>
> >>> ><br>
> >>> > *2.* nepomuk-core installs headers under nepomuk2. \
It's<br> > released<br>
> >>> > independently.<br>
> >>> > *Problem:* Mysterious crashes if both libraries are \
loaded.<br> > >>> ><br>
> >>> > *3.* nepomuk-core installs headers under nepomuk2 and \
the<br> > namespace is<br>
> >>> > changed to nepomuk2.<br>
> >>> > *Problem:* A lot more work :(<br>
> >>><br>
> >>> Well, I suppose we could make this work with some sed \
magic. :P<br> > >>> I would vote for option 3 which could then be \
reverted (or<br> > not) for<br>
> >>> kde5.<br>
> >>><br>
> >>><br>
> >>> I would prefer option 2.<br>
> >>><br>
> >>> The mysterious crashes would only happen if an \
application's plugin<br> > >>> links to the incorrect \
libraries.<br> > >>><br>
> >>> Is that a possibility for us?<br>
> >><br>
> >><br>
> >> I already experienced that. Took me a while to find the reason.<br>
> >><br>
> >><br>
> >> Alright.<br>
> >><br>
> >> I would like the Nepomuk2 namespace and include directories be<br>
> removed for the frameworks, but I guess it is not a big deal if that<br>
> doesn't happen.<br>
> >><br>
> >> ----<br>
> >><br>
> >> Okay, everyone. This is the point where you chime in and say -<br>
> "We're okay with this" or you raise your objections. We would \
like<br> > to get this mess sorted in time for the 4.9 release.<br>
> >><br>
> >><br>
> >><br>
> >><br>
> > _______________________________________________<br>
> > Nepomuk mailing list<br>
</div></div>> > <a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> \
<mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>><br> <div \
class="im">> > <a href="https://mail.kde.org/mailman/listinfo/nepomuk" \
target="_blank">https://mail.kde.org/mailman/listinfo/nepomuk</a><br> > \
_______________________________________________<br> > Nepomuk mailing list<br>
</div>> <a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> <mailto:<a \
href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>><br> <div class="HOEnZb"><div \
class="h5">> <a href="https://mail.kde.org/mailman/listinfo/nepomuk" \
target="_blank">https://mail.kde.org/mailman/listinfo/nepomuk</a><br> ><br>
><br>
><br>
><br>
> --<br>
> Vishesh Handa<br>
><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><span \
style="color:rgb(192,192,192)">Vishesh Handa</span><br><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic