Re: gEDA: Big changes to RC file system

[Ales Hvezda <ahvezda-at-NOSPAMmoria_dot_seul_dot_org>]

Hi Stuart,

[snip]
>These changes meant that I needed to also change gschem, gnetlist,
>gattrib, etc.  Specifically, I now call all the g_rc_parse stuff with
>w_current as the first arg.  w_current now holds a GList of all RC
>files which have been visited, and if a new file is opened, the
>corresponding RC file is also opened if it isn't already open. 
>
>I also refactored code in all the programs which rely upon these
>functions in libgeda.

	This is probably a good idea, however, I never intended the user
to read in multiple different project gafrcs while running a single
instance of gschem, so I worry about the following related scenarios:

1) Picture that you have multiple schematics in muliple directories
(different projects or different revisions of the same schematic)
and you start opening them up and the local gafrc files get read in.
What happens if the gafrc themselves set component-library paths which
break the schematic?  Is this a problem?

Another way to state the above:

2) Unless I have forgotten, but reading in a gafrc affects every
loaded schematic, so schematic A has its gafrc loaded (with its own
component-libraries), then the user loads schematic B and has its gafrc
loaded.  Now the running gschem has two sets of component-libraries
which might clash.  Again, do we care about this problem?

Probably for the casual user, this change won't be too much of a problem,
however I worry about the experienced user who does something and all
of the sudden gschem thinks it's being smart and does something really
stupid or rather unexpected.  I'm probably just being paranoid...


>Question for Ales:  I have tested this stuff on my box and it seems to
>work.  I would like to have others test it too.  I can just upload it
>to CVS, but it represents a lot of changes.  Although I have tested
>it, there is always the chance that it breaks something.   So, hould I
>just close my eyes and upload it, or would you like to look at it
>first?  Or perhaps put it in an experimental branch of the code?  

	Ah to heck with caution.  :)  Check it in and we'll see what
happens.  I'll play with the code when I get a chance.  

								-Ales