X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Wed, 6 Jul 2016 20:33:34 +0200 (CEST)
X-X-Sender:	igor2 AT igor2priv
To:	"James Battat (jbattat AT wellesley DOT edu) [via geda-user AT delorie DOT com]" <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] Exporting a design
In-Reply-To:	<CFAF1482-53BC-4F77-8396-8509F7336455@wellesley.edu>
Message-ID:	<alpine.DEB.2.00.1607062021530.7286@igor2priv>
References:	<C1B27CB8-9811-4101-8166-F8E17D7026FF AT wellesley DOT edu> <alpine DOT DEB DOT 2 DOT 00 DOT 1607061442400 DOT 7286 AT igor2priv> <CFAF1482-53BC-4F77-8396-8509F7336455 AT wellesley DOT edu>
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

On Wed, 6 Jul 2016, James Battat (jbattat AT wellesley DOT edu) [via geda-user AT delorie DOT com] wrote:

>
>> (btw, I'm adding better project file support in pcb-rnd mainly for this use case, see my mail from a few hours ago)
>
> Yes, it was your email that prompted my question!

Ahh, cool! Then the answer in terms of pcb-rnd and project files:

A. mostly the same, make a repo and put in svn externs (or something 
similar in your favorite VCS). The only diff is that then create a project 
file that references the sch and pcb files and configures gsch2pcb-rnd and 
pcb-rnd to use the local libs (before the user and system configured 
ones). This obviously doesn't solve gschem's side, as gschem doesn't 
understand the project file (any scheme wizard volunteer?).

B. after a fruitful chat with dj on IRC, I see another potential option. I 
can imagine a project file that lists some sort of URLs instead of paths 
for the project and for the libs (but the settings part and metadata are 
the same). The other party gets this file and runs an utility that 
downloads/fetches/checks out all the referenced URLs into local files and 
writes back the local paths to the project file. From this point on, we 
are back at solution A, only we didn't let the VCS collect the parts, but 
wrote a tool. Pro: multiple different methods of collecting can be 
configured (wget from anywhere, wget from gedasymbols, cvs from 
gedasymbols, svn checkut, git clone, etc.). Con: needs a downloader tool 
- extra complexity for the user, extra work.

C. in theory all the existing tools could do what the downloader tool does 
in B., e.g. pcb-rnd and gsch2pcb-rnd directly using the footprint lib url 
found in the project file. I would hate this setup, teaching all tools to 
so this task indeed sounds like too much integration. The only benefit 
compared to B is that the complexity of the external downloader tool is 
now burried, hidden and potentially duplicated in other tools - if that's 
a benefit.

(These are not yet possible as I have not yet finished project file 
support; at least A. will be possible within a week or two, then doing B 
is very fast, if anyone needs it.)

- Raw text -