KDE svn structure
Dirk Eschler
i'm not very familiar with the KDE svn repository. Maybe you can help me with
some questions.
How do you checkout a full copy of krusader once it hits kdeextragear? As far
as i understand docs and translations will be separated. There are many
website scripts that run in the background and they rely to have the doc and
po folder inside the application root.
bye,
Dirk
--
Dirk Eschler <esc...@gmail.com>
Fathi Boudra
> As far as i understand docs and translations will be separated. There are many
> website scripts that run in the background and they rely to have the doc and
> po folder inside the application root.
createtarball script is one solution.
the page below explains the release process:
http://extragear.kde.org/home/docs.php
indeed, we can use another script if createtarball isn't good enough.
i think there's a couple of available scripts.
something like:
svn export svn://anonsvn.kde.org/home/kde/trunk/kdereview/krusader
svn svn export svn://anonsvn.kde.org/home/kde/trunk/kdereview/doc/krusader doc
mv doc krusader/
cheers,
Fathi
Dirk Eschler
> > How do you checkout a full copy of krusader once it hits kdeextragear?
> > As far as i understand docs and translations will be separated. There are
> > many website scripts that run in the background and they rely to have the
> > doc and po folder inside the application root.
>
> createtarball script is one solution.
> the page below explains the release process:
> http://extragear.kde.org/home/docs.php
Has the script been moved? There's no trunk/kdesdk.
> indeed, we can use another script if createtarball isn't good enough.
> i think there's a couple of available scripts.
>
> something like:
> svn export svn://anonsvn.kde.org/home/kde/trunk/kdereview/krusader
> svn svn export svn://anonsvn.kde.org/home/kde/trunk/kdereview/doc/krusader
> doc mv doc krusader/
However, i think i can roll my own script once everything is in extragear.
But there's another (bigger) problem - how can i mirror the repository to use
it with trac? For the SourceForge repository i use a hourly cronjob that uses
rsync (as simple as "/usr/bin/rsync -av
krusader.svn.sourceforge.net::svn/krusader/* .").
With the KDE repository that's not possible. 1) They don't seem to provide
rsync and 2) It would be insane to mirror the whole repository.
Subversions svnsync tool, which allows to mirror certain subdirectories, only
works on local repositories, and we don't have shell access to the svn server.
How reliable is svk? Never used it, but as far as i read it's able to mirror a
remote subversion repository.
bye,
Dirk
--
Dirk Eschler <esc...@gmail.com>
http://www.krusader.org
Fathi Boudra
maybe a typo somewhere. right url is:
http://websvn.kde.org/trunk/KDE/kdesdk/scripts/createtarball/
> But there's another (bigger) problem - how can i mirror the repository to use
> it with trac? For the SourceForge repository i use a hourly cronjob that uses
> rsync (as simple as "/usr/bin/rsync -av
> krusader.svn.sourceforge.net::svn/krusader/* .").
> With the KDE repository that's not possible. 1) They don't seem to provide
> rsync and 2) It would be insane to mirror the whole repository.
>
> Subversions svnsync tool, which allows to mirror certain subdirectories, only
> works on local repositories, and we don't have shell access to the svn server.
> How reliable is svk? Never used it, but as far as i read it's able to mirror a
> remote subversion repository.
you can mirror using svk and publish the mirror without any problem.
quick tutorial:
svk depotmap --init
svk mirror svn://anonsvn.kde.org/home/kde/trunk/kdereview/krusader //krusader
svk sync //kdereview
svnserve -d -r ~/.svk/local
in a cron job, add the svk sync.
If you are more familiar with Git (Trac Git plugin), you can do
something similar.
cheers,
Fathi
Dirk Eschler
[...]
> you can mirror using svk and publish the mirror without any problem.
>
> quick tutorial:
> svk depotmap --init
> svk mirror svn://anonsvn.kde.org/home/kde/trunk/kdereview/krusader
> //krusader svk sync //kdereview
> svnserve -d -r ~/.svk/local
Nice, that worked.
We might consider to mirror docs and translations as well. I'll see if can
rebuild the structure once krusader has reached it's final destination in
kdeextragear. Even though that won't be easy - translations are stored by
country rather than by application.
Thanks,
Fathi Boudra
same way as krusader, you mirror in //doc.
> I'll see if can rebuild the structure once krusader has reached it's final destination in
> kdeextragear. Even though that won't be easy - translations are stored by
> country rather than by application.
Is it related to the website scripts ?
Is it problematic to use current structure in KDE svn ?
I'm just wondering what's the problem.
I didn't get the point.
cheers,
Fathi
Dirk Eschler
> > We might consider to mirror docs and translations as well.
>
> same way as krusader, you mirror in //doc.
>
> > I'll see if can rebuild the structure once krusader has reached it's
> > final destination in kdeextragear. Even though that won't be easy -
> > translations are stored by country rather than by application.
>
> Is it related to the website scripts ?
No, the website scripts aren't set in stone, they can be changed...
> Is it problematic to use current structure in KDE svn ?
> I'm just wondering what's the problem.
> I didn't get the point.
The structure in kde's repository is like:
/trunk/l10n-kde4/bg/messages/extragear-xxx/application_name.po
/trunk/l10n-kde4/cz/messages/extragear-xxx/application_name.po
/trunk/l10n-kde4/de/messages/extragear-xxx/application_name.po
...
/trunk/l10n-kde4/fr/docs/extragear-xxx/application_name/
/trunk/l10n-kde4/ru/docs/extragear-xxx/application_name/
...
The structure is okay and to avoid confusion i think the mirror should keep
it. I just thought it might be tricky to mirror only the krusader related bits
into a single repository with svk.
Bye,
Dirk
--
Dirk Eschler <esc...@gmail.com>
http://www.krusader.org
Fathi Boudra
> it. I just thought it might be tricky to mirror only the krusader related bits
> into a single repository with svk.
Thanks for the clarification :)
cheers,
Fathi