X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Tue, 26 Jul 2016 15:00:39 -0400
Message-Id: <201607261900.u6QJ0dLX005528@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20160726183902.GA31144@localhost.localdomain>
	(geda-user AT delorie DOT com)
Subject: Re: [geda-user] repo type for geda-gaf
References: <6a127173-3bcb-a8f3-4704-3ab39a239509 AT ecosensory DOT com>
 <201607251850 DOT u6PIobwh013871 AT envy DOT delorie DOT com>
 <dec6b6ea-42ef-b54f-9c78-f0b92b80e76d AT ecosensory DOT com>
 <76107632-bb6e-8efa-de86-3b8b6df95dcc AT ecosensory DOT com>
 <5797114F DOT 9020308 AT m0n5t3r DOT info>
 <393dfea7-12c5-dee2-f870-4bcdf8975741 AT ecosensory DOT com>
 <201607261550 DOT u6QFo7qh030576 AT envy DOT delorie DOT com> <20160726183902 DOT GA31144 AT localhost DOT localdomain>
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
Precedence: bulk


> It would still (probably) more convenient to have a newer
> version. I would then setup my (slightly old) Debian chroot
> environment on your host to satisfy meets of some of our folks who
> desire to build the geda-gaf Windows port and who would then
> reproduce it as is.

Yup, that's another good reason for the migration.

> > > I have an account with atlantic.net and could start it up to test
> > > out...  I even have a store credit with them that I will not be able
> > 
> > Relying on the community to pay for hosting is unreliable in our
> > community, and I can host it for free :-)
> 
> And for ever ? ;-) 

Well, when I eventually die I suppose someone else will have to take
ownership of it ;-)

But if it's just a VM image, it can be migrated elsewhere pretty
easily.

> > The complex part is managing the shared data between all the hosts
> > that make up gedaproject.org
> 
> What programs are you using?
> Could rsync help anywhere?

I mean, if you have more than one VM, they need to share data somehow.
With one VM it's all on one filesystem and one OS, which simplifies a
lot of the problems.

At the moment, it's all one host, except for launchpad, which we found
to be a nightmare to interact with reliably.