X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Wed, 29 Mar 2017 15:40:38 +0200 (CEST)
X-X-Sender:	igor2 AT igor2priv
To:	geda-user AT delorie DOT com
X-Debug:	to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From:	gedau AT igor2 DOT repo DOT hu
Subject:	Re: [geda-user] gedasymbols.org and EDAKrill - need your opinion
In-Reply-To:	<20170329125832.1C3B9809DB74@turkos.aspodata.se>
Message-ID:	<alpine.DEB.2.00.1703291527270.27212@igor2priv>
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1703250637200 DOT 27212 AT igor2priv> <20170329125832 DOT 1C3B9809DB74 AT turkos DOT aspodata DOT se>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Hello Karl,

On Wed, 29 Mar 2017, karl AT aspodata DOT se wrote:

> Igor2:

> in nowhere. Is there any way of solving that with svn ? Or is it
> possible to have a regular import from a git repo to svn ?

The offline case for read is trivial: you check out the whole db when you 
are online, you have it on disk, you work from it.

Upload: svn commit when you are next online.

I don't plan git mirrors or syncing to git on server side. I don't 
know what tools are available for git->svn on client side.

> Is there any possibility to set up mirrors to share the bandwidth,
> would that be possible with svn, can I set up such a mirror ?

Yup. There is a tool introduced recently, called svnrdump. It can dump a 
remote repository locally, even incrementally. So the process would be:

1. set up a local repository somewhere (can even be a file://, doesn't 
need to be served on the net, doesn't need root, etc.)

2. svnrdump edakrill and svnadmin load the dump into that local repo (can 
be piped) - svnrdump can be done anonymously, you don't need any extra 
server support or privileges for this

3. keep track on the last revision you have imported and do an incremental 
rdump from tiem to time

4. repeat 3 periodically

I recommend making such mirror repositories read-only, as there won't be 
any means to merge changes among sites.

You shoudl do this only if you want to browse the history for some reason. 
If you only want to have all the footprints/symbols, a plain checkout is 
enough. Having the history won't make it easier to commit.


Maybe off-topic: mirroring the web site (with all the CGIs) is somewhat 
harder - I didn't design them to be easily installable on random systems. 
Probably the simplest way would be to set up some virtual hosting 
(vserver, uml, qemu/virtualbox or at least a chroot) and provide me access 
so I'd install the new versions. If there are dozens of server admins 
rushing to offer mirrors, I can make the whole CGI part much easier to 
install, maybe pack .debs.

Regards,

Igor2

- Raw text -