[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-sdk-devel
Subject:    Re: [Kde-scm-interest] Layout of "lokalize" and "kompare" git repos with plugins integrated (was: Re
From:       Sebastian_Dörner <sebastian () sebastian-doerner ! de>
Date:       2012-12-20 0:01:59
Message-ID: CA+_kBjBPU9s_atVNDL=kF7NwKy2ndhhu5J5ay8Si2XfSoHTEbA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 19 December 2012 18:22, Albert Astals Cid <aacid@kde.org> wrote:

> El Dimarts, 18 de desembre de 2012, a les 18:07:03, Jeremy Whiting va
> escriure:
> > Albert,
> >
> > I got all of kdesdk subfolders to build standalone using the attached
> > (huge) patch.  I want to get someone besides myself to take a look
> before I
> > commit it though, but here it makes it so kdesdk can be built as one
> > module, and also each subfolder (except docs) can be built by itself.
>
> One of the thing we did for kdegames is move the docs inside the modules
> they
> belong to in svn (before moving to git) this way we could check that
> installing the svn repo and installing all the git modules (without any
> change) gave exactly the same result.
>
Sorry if this comes a bit late, but this is probably a bad idea. The
current rules expect the docs where they are and the conversion puts
docs/$APP into $APP/docs. Getting this right was quite a hassle (e.g. as
some docs originally came from the common docs/scripts directory), and I
wouldn't want to touch that again.


> I can help with that if you want (it needs more than just the move, needs a
> small tweak with the CMakeLists.txt)
>
> Cheers,
>   Albert
>
>
> > I
> > removed quite a bit from the top level CMakeLists.txt so it's just a
> bunch
> > of add_subdirectory calls.  I also took out pimlibs detection and
> couldn't
> > find any subdir that needed/used it.  That was either in there from
> > something that has since been removed or is an optional dependency for
> > something.  If anyone knows which we may need to tweak this before
> > committing.
> >
> > thanks,
> > Jeremy
> >
> > On Wed, Dec 12, 2012 at 11:44 AM, Albert Astals Cid <aacid@kde.org>
> wrote:
> > > El Dimarts, 11 de desembre de 2012, a les 18:03:07, Jeremy Whiting va
> > >
> > > escriure:
> > > > Hello all,
> > > >
> > > > Thanks to some awesome students in Brazil we have most (maybe all) of
> > > > the
> > > > kdesdk migration rules written.  I have done an initial conversion
> with
> > >
> > > the
> > >
> > > > existing rules last night and pushed to scratch repos on
> > > > http://quickgit.kde.org/scratch/whiting/(cervisia, dolphin-plugins,
> > > > kapptemplate, kcachegrind, kde-dev-scripts, kde-dev-utils, kompare,
> > > > lokalize, okteta, poxml, strigi-analyzers, and umbrello).git  If
> each of
> > > > you that is a maintainer of one of the above projects could please
> clone
> > > > the repositories, make sure no tags or branches that you expect are
> > >
> > > missing
> > >
> > > > (and no extra branches that don't belong to your project are in
> there)
> > >
> > > then
> > >
> > > > mark the "Maintainer approved" column on
> > > > http://community.kde.org/KDESDK/Git_Migration#Migration_Rules I
> would
> > > > really appreciate it.
> > > >
> > > > The umbrello developers and I are hoping we can do the actual
> conversion
> > > > this weekend before the 4.10 RC 1 tag, but in order for that to
> happen
> > > > we
> > > > need these all to be verified and I need to make it so we can release
> > > > the
> > > > 4.10 tarball from git repos (I've done that before for kde-edu and
> > > > kde-accessibility, but can't recall how that's done, so will figure
> that
> > > > out in the next few days).
> > >
> > > The projects don't build standalone (at least poxml doesn't).
> > >
> > > I suggest we/you do the same we did with kdegames, that is, make them
> > > build
> > > standalone in svn before the split, so the splitted repo can be
> verified
> > > to
> > > build correctly without any "manual" modification.
> > >
> > > Cheers,
> > >
> > >   Albert
> > >
> > > > thanks,
> > > > Jeremy Whiting
> > > >
> > > > P.S. It would have been much nicer if there were a kdesdk mailing
> list,
> > >
> > > but
> > >
> > > > I guess since the module is a group of such separate utilities one
> has
> > > > never been created, should we create one?
> > > >
> > > > On Mon, Jun 18, 2012 at 11:51 AM, Nick Shaforostoff <shafff@ukr.net>
> > >
> > > wrote:
> > > > > > > Currently:
> > > > > > > repo name / display name: lokalize / Lokalize
> > > > > > > description: Computer-aided i18n translation
> > > > >
> > > > > just 'Computer-aided translation'
> > > > >
> > > > > > > project manager (user id on projects.kde.org needed): ?, ?,
> ...
> > > > >
> > > > > my id is 'shaforo'
> > > > >
> > > > > > Data needed!
> > > > > >
> > > > > > > layout in kdesdk:
> > > > > > > /
> > > > > > > +- lokalize
> > > > > > > +- strigi-analyzer
> > > > > > >
> > > > > > >    +- po
> > > > > > >    +- ts
> > > > > > >    +- xliff
> > > > > > >
> > > > > > > +- thumbnailers
> > > > > > >
> > > > > > >    +- po
> > > > >
> > > > > i don't really care, but personally i'm for this layout, because
> > >
> > > lokalize
> > >
> > > > > depends on analyzers, but not vice-versa.
> > > > > _______________________________________________
> > > > > Kde-scm-interest mailing list
> > > > > Kde-scm-interest@kde.org
> > > > > https://mail.kde.org/mailman/listinfo/kde-scm-interest
> _______________________________________________
> Kde-scm-interest mailing list
> Kde-scm-interest@kde.org
> https://mail.kde.org/mailman/listinfo/kde-scm-interest
>

[Attachment #5 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 19 \
December 2012 18:22, Albert Astals Cid <span dir="ltr">&lt;<a \
href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>&gt;</span> wrote:<br> \
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">El Dimarts, 18 de desembre de 2012, a les 18:07:03, Jeremy \
Whiting va<br> escriure:<br>
<div class="im">&gt; Albert,<br>
&gt;<br>
&gt; I got all of kdesdk subfolders to build standalone using the attached<br>
&gt; (huge) patch.  I want to get someone besides myself to take a look before I<br>
&gt; commit it though, but here it makes it so kdesdk can be built as one<br>
&gt; module, and also each subfolder (except docs) can be built by itself.<br>
<br>
</div>One of the thing we did for kdegames is move the docs inside the modules \
they<br> belong to in svn (before moving to git) this way we could check that<br>
installing the svn repo and installing all the git modules (without any<br>
change) gave exactly the same result.<br></blockquote><div style>Sorry if this comes \
a bit late, but this is probably a bad idea. The current rules expect the docs where \
they are and the conversion puts docs/$APP into $APP/docs. Getting this right was \
quite a hassle (e.g. as some docs originally came from the common docs/scripts \
directory), and I wouldn&#39;t want to touch that again.</div> <div \
style><br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
I can help with that if you want (it needs more than just the move, needs a<br>
small tweak with the CMakeLists.txt)<br>
<br>
Cheers,<br>
  Albert<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
&gt; I<br>
&gt; removed quite a bit from the top level CMakeLists.txt so it&#39;s just a \
bunch<br> &gt; of add_subdirectory calls.  I also took out pimlibs detection and \
couldn&#39;t<br> &gt; find any subdir that needed/used it.  That was either in there \
from<br> &gt; something that has since been removed or is an optional dependency \
for<br> &gt; something.  If anyone knows which we may need to tweak this before<br>
&gt; committing.<br>
&gt;<br>
&gt; thanks,<br>
&gt; Jeremy<br>
&gt;<br>
&gt; On Wed, Dec 12, 2012 at 11:44 AM, Albert Astals Cid &lt;<a \
href="mailto:aacid@kde.org">aacid@kde.org</a>&gt; wrote:<br> &gt; &gt; El Dimarts, 11 \
de desembre de 2012, a les 18:03:07, Jeremy Whiting va<br> &gt; &gt;<br>
&gt; &gt; escriure:<br>
&gt; &gt; &gt; Hello all,<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Thanks to some awesome students in Brazil we have most (maybe all) \
of<br> &gt; &gt; &gt; the<br>
&gt; &gt; &gt; kdesdk migration rules written.  I have done an initial conversion \
with<br> &gt; &gt;<br>
&gt; &gt; the<br>
&gt; &gt;<br>
&gt; &gt; &gt; existing rules last night and pushed to scratch repos on<br>
&gt; &gt; &gt; <a href="http://quickgit.kde.org/scratch/whiting/(cervisia" \
target="_blank">http://quickgit.kde.org/scratch/whiting/(cervisia</a>, \
dolphin-plugins,<br> &gt; &gt; &gt; kapptemplate, kcachegrind, kde-dev-scripts, \
kde-dev-utils, kompare,<br> &gt; &gt; &gt; lokalize, okteta, poxml, strigi-analyzers, \
and umbrello).git  If each of<br> &gt; &gt; &gt; you that is a maintainer of one of \
the above projects could please clone<br> &gt; &gt; &gt; the repositories, make sure \
no tags or branches that you expect are<br> &gt; &gt;<br>
&gt; &gt; missing<br>
&gt; &gt;<br>
&gt; &gt; &gt; (and no extra branches that don&#39;t belong to your project are in \
there)<br> &gt; &gt;<br>
&gt; &gt; then<br>
&gt; &gt;<br>
&gt; &gt; &gt; mark the &quot;Maintainer approved&quot; column on<br>
&gt; &gt; &gt; <a href="http://community.kde.org/KDESDK/Git_Migration#Migration_Rules" \
target="_blank">http://community.kde.org/KDESDK/Git_Migration#Migration_Rules</a> I \
would<br> &gt; &gt; &gt; really appreciate it.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; The umbrello developers and I are hoping we can do the actual \
conversion<br> &gt; &gt; &gt; this weekend before the 4.10 RC 1 tag, but in order for \
that to happen<br> &gt; &gt; &gt; we<br>
&gt; &gt; &gt; need these all to be verified and I need to make it so we can \
release<br> &gt; &gt; &gt; the<br>
&gt; &gt; &gt; 4.10 tarball from git repos (I&#39;ve done that before for kde-edu \
and<br> &gt; &gt; &gt; kde-accessibility, but can&#39;t recall how that&#39;s done, \
so will figure that<br> &gt; &gt; &gt; out in the next few days).<br>
&gt; &gt;<br>
&gt; &gt; The projects don&#39;t build standalone (at least poxml doesn&#39;t).<br>
&gt; &gt;<br>
&gt; &gt; I suggest we/you do the same we did with kdegames, that is, make them<br>
&gt; &gt; build<br>
&gt; &gt; standalone in svn before the split, so the splitted repo can be \
verified<br> &gt; &gt; to<br>
&gt; &gt; build correctly without any &quot;manual&quot; modification.<br>
&gt; &gt;<br>
&gt; &gt; Cheers,<br>
&gt; &gt;<br>
&gt; &gt;   Albert<br>
&gt; &gt;<br>
&gt; &gt; &gt; thanks,<br>
&gt; &gt; &gt; Jeremy Whiting<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; P.S. It would have been much nicer if there were a kdesdk mailing \
list,<br> &gt; &gt;<br>
&gt; &gt; but<br>
&gt; &gt;<br>
&gt; &gt; &gt; I guess since the module is a group of such separate utilities one \
has<br> &gt; &gt; &gt; never been created, should we create one?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; On Mon, Jun 18, 2012 at 11:51 AM, Nick Shaforostoff &lt;<a \
href="mailto:shafff@ukr.net">shafff@ukr.net</a>&gt;<br> &gt; &gt;<br>
&gt; &gt; wrote:<br>
&gt; &gt; &gt; &gt; &gt; &gt; Currently:<br>
&gt; &gt; &gt; &gt; &gt; &gt; repo name / display name: lokalize / Lokalize<br>
&gt; &gt; &gt; &gt; &gt; &gt; description: Computer-aided i18n translation<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; just &#39;Computer-aided translation&#39;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt; project manager (user id on <a \
href="http://projects.kde.org" target="_blank">projects.kde.org</a> needed): ?, ?, \
...<br> &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; my id is &#39;shaforo&#39;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; Data needed!<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt; layout in kdesdk:<br>
&gt; &gt; &gt; &gt; &gt; &gt; /<br>
&gt; &gt; &gt; &gt; &gt; &gt; +- lokalize<br>
&gt; &gt; &gt; &gt; &gt; &gt; +- strigi-analyzer<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;    +- po<br>
&gt; &gt; &gt; &gt; &gt; &gt;    +- ts<br>
&gt; &gt; &gt; &gt; &gt; &gt;    +- xliff<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt; +- thumbnailers<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;    +- po<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; i don&#39;t really care, but personally i&#39;m for this layout, \
because<br> &gt; &gt;<br>
&gt; &gt; lokalize<br>
&gt; &gt;<br>
&gt; &gt; &gt; &gt; depends on analyzers, but not vice-versa.<br>
&gt; &gt; &gt; &gt; _______________________________________________<br>
&gt; &gt; &gt; &gt; Kde-scm-interest mailing list<br>
&gt; &gt; &gt; &gt; <a \
href="mailto:Kde-scm-interest@kde.org">Kde-scm-interest@kde.org</a><br> &gt; &gt; \
&gt; &gt; <a href="https://mail.kde.org/mailman/listinfo/kde-scm-interest" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-scm-interest</a><br> \
_______________________________________________<br> Kde-scm-interest mailing list<br>
<a href="mailto:Kde-scm-interest@kde.org">Kde-scm-interest@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-scm-interest" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-scm-interest</a><br> \
</div></div></blockquote></div><br></div></div>



_______________________________________________
kde-sdk-devel mailing list
kde-sdk-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-sdk-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic