X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Mon, 20 Feb 2017 20:33:19 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] Recent gschem-PCB import problem?
In-Reply-To: <CAM2RGhQkLag05P-tpvuReg3Y-42S4uu-U4Uk_0z8Q0sk6x34bA@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1702202013001.1575@nimbus>
References: <1487162236 DOT 3011 DOT 9 DOT camel AT linetec> <alpine DOT DEB DOT 2 DOT 00 DOT 1702151631080 DOT 7286 AT igor2priv> <1487176819 DOT 3011 DOT 27 DOT camel AT linetec> <CAJXU7q-HcAcwnXxMvop6foh-ZDkeZSUtGNeT7hEEn4b04gEReQ AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 11 DOT 1702152257280 DOT 1532 AT nimbus>
 <CAHdUXzLP-2-0jbMskxNs+TU59REMdHU-Uwv2PH_q969c_uTgzA AT mail DOT gmail DOT com> <CAHdUXzL90qYtBnh3c0sXOeDNoqV=mfS7ucqu5zfQrGm61G6qcQ AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 20 DOT 1702192044220 DOT 9009 AT nimbus> <CAM2RGhReqeNKCgd-XkyP2E=-YzmAxBH4tfnZ_r6hawPaStWcBQ AT mail DOT gmail DOT com>
 <alpine DOT DEB DOT 2 DOT 20 DOT 1702192141300 DOT 25772 AT nimbus> <CAM2RGhQkLag05P-tpvuReg3Y-42S4uu-U4Uk_0z8Q0sk6x34bA AT mail DOT gmail DOT com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Note-from-DJ: This may be spam
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

On Mon, 20 Feb 2017, Evan Foss (evanfoss AT gmail DOT com) [via 
geda-user AT delorie DOT com] wrote:
> That is a fair point. I guess it's the lack of options that doesn't sit 
> well with me. I wish gEDA or Lepton would let us opt out of scheme. My 
> distro didn't even package guile-2.x.

With the way the code is structured right now, that wouldn't be easy. 
Even if the internal dependencies on Scheme could be avoided, you still 
wouldn't be able to execute configuration files or use the netlister the 
normal way (the current version can run non-Scheme backends, though).

It would be possible to switch to a non-Scheme configuration system and 
invoke the netlister another way.  But that would require a lot of work, 
and doing this in a way that makes sense would most probably break 
compatibility with more complex existing Scheme setups.