X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-TMN:	[sYQ04a6JVR2z7ldgag9QzwTCc1TNhqdP]
X-Originating-Email:	[vuokko AT msn DOT com]
Message-ID:	<DUB125-W81B730FD43CB242CEA5D8EC67E0@phx.gbl>
From:	"Hannu Vuolasaho (vuokko AT msn DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	"geda-user AT delorie DOT com" <geda-user AT delorie DOT com>
Subject:	RE: [geda-user] multiple gEDA users sharing networked libraries
Date:	Thu, 13 Aug 2015 02:16:08 +0300
Importance:	Normal
In-Reply-To:	<87k2t0nq8y.fsf@rover.gag.com>
References:	<55CB4F8A DOT 9020506 AT envinsci DOT co DOT uk>,<87k2t0nq8y DOT fsf AT rover DOT gag DOT com>
MIME-Version:	1.0
X-OriginalArrivalTime:	12 Aug 2015 23:16:09.0127 (UTC) FILETIME=[DF222370:01D0D554]
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t7CNGEon020298
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

Bdale wrote:
>
> "Matt Rhys-Roberts (matt DOT rhys-roberts AT envinsci DOT co DOT uk) [via
> geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> writes:
>
>> We're considering keeping symbol & footprint libraries on a networked
>> server, so that several designers can refer and contribute to common
>> components and workfiles.
>>
>> Is anyone else already doing this? How's it going? Any pro's and con's
>> to this approach?

On NFS or similar system concurrent editing one file will fail. But solution
is totally ugly deeply hierarchy in schematics and communication who is
touching where.

Symbols and footprints are easily shareable.

In version control there isn't that much trouble ahead.
>
> I can't imagine living in a shared network filesystem without revision
> control, way too many things could go wrong!

+1 for git repo. Even if project has linear progress, conflicts are easy to
resolve and someday git is needed somewhere. So teaching git add commit
pull push is valuable skill.

Any version control will work and back-upping is important. There is only small
difference between shared and shred stuff.

And now something completely different. Just a normal day in Finland.

And when storm hit to one house which I was occupying in 2013, I just waited
for it to settle. It was Friday morning when I went to roof and put plastic patch
on hole which storm had torn, took backup generator and connected freezer
and set it to maximum freeze.

I cleaned up places, and fixed stuff which was most irritating.
When temperature in freezer was -30, I stopped generator, drove few kilometres
and found the tree on the power line. Then I had to drive some kilometres more
to get cellular reception to call power company. Base stations seemed to be
down also.

I drove back to house, got 60Ah 12V car battery, 20 litres of fresh water and all
easily spoiling food  from fridge. Then I drove to another cabin which has no
electricity at all. I cleaned up places there too but storm had been much lighter there.
Then I heated sauna, bathed and had dinner and made coffee.

When sun set down I had those batteries, laptop and I designed some schematics
to a hobby project. It is much harder without google. And it was nice weekend. 
On Monday I had power back on and some more cleaning and fixing to do.
 
So yes. People design schematics when 21st century gets broken. It is important
to remember keep reserve of fresh water and battery.

--
Hannu Vuolasaho
 		 	   		  

- Raw text -