<br><br><div class="gmail_quote">On Thu, May 17, 2012 at 1:06 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"><br>
<br>
On 05/16/2012 09:16 PM, Vishesh Handa wrote:<br>
><br>
><br>
> On Thu, May 17, 2012 at 12:29 AM, 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>
> Pushed my stuff to branch "feature/nepomuk2Includes".<br>
><br>
> Feel free to implement Ivan's fancier solution. In that case my branch<br>
> might at least help in finding the places where stuff needs replacing.<br>
> If you do not I would appreciate a look over my branch to check if I<br>
> missed sth.<br>
><br>
><br>
> I will implement it, but not today. You'd missed one place. I've<br>
> corrected it.<br>
><br>
> So now you just need to use the same script on your scratch<br>
> repositories.<br>
<br>
</div>Well, if you want to implement Ivan's idea that should be applied to the<br>
scratch repos, too.<br></blockquote><div><br>Lets just get this done, before we try anything fancy. The hard feature freeze is tomorrow. <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>
> Also, do you know anything about translations?<br>
<br>
</div>Hm, we should ask the l10n team about it before removing the code from<br>
kde-runtime.<br></blockquote><div><br>Probably. Do you want me to email everyone? (packagers, release-team and i18n)<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 HOEnZb"><br>
><br>
><br>
> Cheers,<br>
> Sebastian<br>
><br>
> On 05/16/2012 08:37 PM, Vishesh Handa wrote:<br>
> ><br>
> ><br>
> > On Thu, May 17, 2012 at 12:02 AM, 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>
</div><div class="im HOEnZb">> > <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>
</div><div class="im HOEnZb">> > 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>
> > I say let's postpone them, they are still in kdelibs.<br>
> ><br>
> ><br>
> > The facets are quite weird and I am not sure about releasing<br>
> them again.<br>
> > The ui stuff - not sure.<br>
> ><br>
> ><br>
> > We have all the runtime stuff and nepomuk-core, that's all that<br>
> matters<br>
> > 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<br>
> BEGIN_NEPOMUK_NAMESPACE. If<br>
> > you want I can take care of it.<br>
> ><br>
> ><br>
> > > On Wed, May 16, 2012 at 11:49 PM, Sebastian Trüg<br>
> <<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>><br>
> > <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>>><br>
</div><div class="im HOEnZb">> > > <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>><br>
> <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>
</div><div class="HOEnZb"><div class="h5">> > > 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<br>
> > "KDE/Base"?<br>
> > > I suppose questions like these have already been discussed<br>
> > 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>
> <mailto:<a href="mailto:ivan.cukic@gmail.com">ivan.cukic@gmail.com</a>><br>
> > <mailto:<a href="mailto:ivan.cukic@gmail.com">ivan.cukic@gmail.com</a> <mailto:<a href="mailto:ivan.cukic@gmail.com">ivan.cukic@gmail.com</a>>><br>
> > > <mailto:<a href="mailto:ivan.cukic@gmail.com">ivan.cukic@gmail.com</a><br>
> <mailto:<a href="mailto:ivan.cukic@gmail.com">ivan.cukic@gmail.com</a>> <mailto:<a href="mailto:ivan.cukic@gmail.com">ivan.cukic@gmail.com</a><br>
> <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<br>
> 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<br>
> > namespaces in<br>
> > > > the method definitions.<br>
> > > ><br>
> > > >> I don't know, thinking that Nepomuk2 namespace is looking<br>
> > rather<br>
> > > ugly :)<br>
> > > ><br>
> > > > it is indeed.<br>
> > > ><br>
> > > >> The dirtiest solution library-wise would be to have<br>
> > everything in<br>
> > > NepomukCore::Nepomuk::Something so that the only change<br>
> in the<br>
> > > current code of nepomuk users would be a using namespace<br>
> > 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<br>
> > <<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a><br>
> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>>><br>
</div></div><div class="HOEnZb"><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>><br>
> <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>
> > > >> 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<br>
> > <<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a><br>
> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>>><br>
> > > <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>><br>
> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>>>><br>
> > > >><br>
> > > >>> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>><br>
> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>>><br>
> > <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a> <mailto:<a href="mailto:trueg@kde.org">trueg@kde.org</a>><br>
> <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.<br>
> > Kdelibs<br>
> > > is not<br>
> > > >>> touched.<br>
> > > >>> > *Problem:* Overlapping headers and possible<br>
> mysterious<br>
> > > crashes if both<br>
> > > >>> > libraries are loaded.<br>
> > > >>> ><br>
> > > >>> > *2.* nepomuk-core installs headers under<br>
> nepomuk2. It's<br>
> > > released<br>
> > > >>> > independently.<br>
> > > >>> > *Problem:* Mysterious crashes if both<br>
> libraries are<br>
> > loaded.<br>
> > > >>> ><br>
> > > >>> > *3.* nepomuk-core installs headers under nepomuk2<br>
> > 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<br>
> some sed<br>
> > magic. :P<br>
> > > >>> I would vote for option 3 which could then be<br>
> 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<br>
> > 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<br>
> the reason.<br>
> > > >><br>
> > > >><br>
> > > >> Alright.<br>
> > > >><br>
> > > >> I would like the Nepomuk2 namespace and include<br>
> directories be<br>
> > > removed for the frameworks, but I guess it is not a big deal<br>
> > if that<br>
> > > doesn't happen.<br>
> > > >><br>
> > > >> ----<br>
> > > >><br>
> > > >> Okay, everyone. This is the point where you chime in<br>
> and say -<br>
> > > "We're okay with this" or you raise your objections. We<br>
> 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>
> > > > <a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>><br>
> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>>><br>
> > <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>><br>
> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>>>><br>
> > > > <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>
> > > <a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>><br>
> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>>><br>
> > <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>><br>
> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a> <mailto:<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>>>><br>
> > > <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>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Vishesh Handa<br>
> ><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>