<br><br><div class="gmail_quote">On Wed, Aug 18, 2010 at 7:24 AM, Andreas Pakulat <span dir="ltr"><<a href="mailto:apaku@gmx.de">apaku@gmx.de</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 18.08.10 00:23:07, Friedrich W. H. Kossebau wrote:<br>
> Mardi, le 17 août 2010, à 22:28, Aleix Pol a écrit:<br>
> > On Thu, Aug 12, 2010 at 11:11 PM, Friedrich W. H. Kossebau<br>
> > <<a href="mailto:kossebau@kde.org">kossebau@kde.org</a><br>
> > > wrote:<br>
</div><div><div></div><div class="h5">> > > now that Okteta 0.5.0 is released, also all the headers for the Okteta<br>
> > > libs are published for the first time, so that 3rd-party developers can<br>
> > > make use of<br>
> > > these libs in their software. Well, also 1st-party developers :)<br>
> > ><br>
> > > Thus I just gave some polish to the Okteta plugin for KDevelop 4.0 I<br>
> > > started<br>
> > > at the Kate-KDevelop sprint in Berlin early this year. I think it is<br>
> > > ready for<br>
> > > a first release now. Find it at<br>
> > > <a href="http://websvn.kde.org/trunk/playground/devtools/kdevelop4-extra-" target="_blank">http://websvn.kde.org/trunk/playground/devtools/kdevelop4-extra-</a><br>
> > > plugins/okteta/<br>
> > ><br>
> > > Now I wonder:<br>
> > > What to do? :)<br>
> > > Where (repo, folder) would the released branch of the plugin end?<br>
> > > How/where do I develop the version for KDevelop 4.1?<br>
> > ><br>
> > > So could someone please review the code and help with adding it to the<br>
> > > official plugins (if accepted as such)? Millian, at Akademy you showed<br>
> > > interest to help with this, still possible? :)<br>
> > ><br>
> > > There is still one problem (but on KDevelop side):<br>
> > > in the filesystem tool in the RMB menu all actions from plugins are added<br>
> > > once<br>
> > > more if the menu gets shown, so by the time appear x times. Alexander, at<br>
> > > Akademy you said you have a fix for this, but I still see this with what<br>
> > > I get<br>
> > > if I compile the kdevplatform 1.0 and kdevelop 4.0 branches. Strangely<br>
> > > enough<br>
> > > the KDevelop (1.0.0, 4.0.0) I use here on (K)Ubuntu does not have this<br>
> > > problem. Will this be ixed in 4.0.2/1.0.x? Could I help?<br>
> > ><br>
> > > Some blog blabla for more background:<br>
> > ><br>
> > > <a href="http://frinring.wordpress.com/2010/02/16/okteta-going-for-kdevelop-and-ka" target="_blank">http://frinring.wordpress.com/2010/02/16/okteta-going-for-kdevelop-and-ka</a><br>
> > > te/<br>
> > > <a href="http://frinring.wordpress.com/2010/07/27/akademy-development-catalysator" target="_blank">http://frinring.wordpress.com/2010/07/27/akademy-development-catalysator</a><br>
> > > /<br>
> ><br>
</div></div><div class="im">> > Since we don't want to have oktetalibs installed as a kdevelop dependency,<br>
><br>
> You mean both hard and optionally dependency?<br>
<br>
</div>Even though Aleix is one of the maintainers, I disagree with him on<br>
this. We already have an optional runtime-dep on kdesdk in kdevplatform,<br>
so IMHO it would be ok to have an optional build-time dep on kdesdk in<br>
kdevelop for the okteta-plugin. In particular because kdevelop is now in<br>
'extragear' (well, will be again once its on <a href="http://git.kde.org" target="_blank">git.kde.org</a>), so there's no<br>
technical problem with that.<br></blockquote><div><br></div><div>Well, the main problem I see here is that the user/packager will never be sure which ones are the really important dependencies.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> > I guess the best would be that you install kdevelop support together with<br>
> > Okteta and KDevelop will detect that automatically.<br>
><br>
> Given that I can't add that to SC 4.5 and that there will be multiple KDevelop<br>
> releases with incompatible plugin versions in the meantime... sorry, don't<br>
> agree that this is the best :)<br>
><br>
> > You can release the KDevelop plugin separately also, what would you prefer<br>
> > to do?<br>
><br>
> Hm, what would packagers prefer? How do you (plan to) handle plugins for<br>
> QtDesigner, KDiff/Kompare and others which depend on other libs? Will there be<br>
> some KDevelop-Addon module, next to KDevPlatform and KDevelop? That is what I<br>
> would prefer to have the plugin in. Could be the starting plugin for that<br>
> module?<br>
> Where else do you consider all the stuff to end which is currently in<br>
> playground/devtools/kdevelop4-extra-plugins?<br>
<br>
</div>I think packagers would be preferring to be able to package those<br>
plugins separately. So planning a bit into the future I think it would<br>
make sense to use a separate git repo for each, but bundling those that<br>
we 'officially' maintain as a kdevplatform-plugins or something like<br>
that (we had that in extragear/sdk too). We'd need to see how to release<br>
this stuff, i.e. wether the plugins can do individual releases or we<br>
always only release everything together (or a mix of both).<br></blockquote><div><br></div><div>I agree with that, we could get a new gitorious repo for that and release it together with 4.1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Andreas<br>
<br>
--<br>
You've been leading a dog's life. Stay off the furniture.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</div></div></blockquote></div><br>