www.delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2021/05/28/14:23:36

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Fri, 28 May 2021 20:22:26 +0200 (CEST)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "karl AT aspodata DOT se [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] errors in git gschem
In-Reply-To: <20210528173138.5441D83B0DDA@turkos.aspodata.se>
Message-ID: <alpine.DEB.2.21.2105282009480.25954@nimbus>
References: <20210527152030 DOT 03D81832CA7E AT turkos DOT aspodata DOT se> <20210528121930 DOT 617BC83B0DDA AT turkos DOT aspodata DOT se> <20210528160449 DOT 9E70083B0DDA AT turkos DOT aspodata DOT se> <alpine DOT DEB DOT 2 DOT 21 DOT 2105281836210 DOT 3565 AT nimbus> <20210528173138 DOT 5441D83B0DDA AT turkos DOT aspodata DOT se>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
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 Fri, 28 May 2021, karl AT aspodata DOT se [via geda-user AT delorie DOT com] wrote:
> Sooo, now I'm confused, does current gschem use both ~/.gEDA and 
> ~/.config/gEDA, with same named files in them ?

There are two different kinds of configuration files:

1) gafrc/gschemrc/gschem-gtkrc and their system-* variants.  These files 
are looked for in PREFIX/share/gEDA/, ~/.gEDA/, and the directory of the 
edited file.

2) geda.conf, geda-user.conf, geda-system.conf.  These files are looked 
for in /etc/xdg/gEDA/, ~/.config/gEDA/, and both the current working 
directory and the directory of the edited file themselves and all their 
parent directories up to the file system root.

This doesn't necessarily make sense, and changing it is on the very top of 
my TODO list.  However, getting gEDA/gaf configuration right isn't a 
trivial thing to do, and I want to make sure to neither add a third, 
conflicting configuration mechanism nor to invent an everything-in-one 
solution that turns out to be a maintainability nightmare.  I think I've 
figured out most things, but right now, I simply lack the capacity for a 
change of that scale.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019