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.
> 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.
Am Montag 08 Juni 2009 21:14:03 schrieb Fathi Boudra:
> > 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.
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.
> 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.
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.
> 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 ? Is it problematic to use current structure in KDE svn ? I'm just wondering what's the problem. I didn't get the point.
Am Dienstag 09 Juni 2009 15:35:44 schrieb Fathi Boudra:
> > 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 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.
> 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.
|
