X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Peter TB Brett <peter AT peter-b DOT co DOT uk>
Subject: Re: [geda-user] [RFC] Major changes to symbol/schematic libraries in geda-gaf
Date: Tue, 10 Sep 2013 06:29:43 +0100
Lines: 53
Message-ID: <87sixdi6rc.fsf@harrington.peter-b.co.uk>
References: <87ob83dodl DOT fsf AT harrington DOT peter-b DOT co DOT uk>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: cpc4-oxfd23-2-0-cust628.4-3.cable.virginmedia.com
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:gwbTmGdoFzPUB5Ge8LUmYR1rB/s=
Reply-To: geda-user AT delorie DOT com

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi all,

Rather than reply to all messages individually and fragment the
discussion further, here are my thoughts on the feedback that I've
received so far.

=2D I'll add the ability to obtain a resource X that's located in the same
  library as another resource Y.  If there's no X corresponding to Y,
  the library will fail to resolve X (although a program might use a
  fallback method that just looks up X normally).  This won't be used by
  gschem, although other gEDA-related programs might want it.

=2D "geda-gaf" is the XDG subdirectory used by the configuration system, so
  the library system ought to use it too.  By convention, the XDG
  subdirectory is the same as the name of the package, and the package
  is called "geda-gaf".  If your scripting language cannot cope with the
  character 0x2D, you need a new scripting language.  Let's not discuss
  the colour of this particular bike shed any further.

=2D Several people have mentioned the benefits of a project resource
  cache.  I agree with almost all of the points made --- a project
  resource cache is a great idea.  Let's have one.  But I'm fed up with
  having things in gEDA that work "sort of".  If I'm designing a new
  subsystem, I want it to work *properly*.  If we're going to have a
  design cache, let's have a design cache that behaves like a cache,
  looks like a cache to programs and provides an API that lets you carry
  out cache-specific operations.  Let's *not* shoehorn it into the
  library system by using special magically-name project libraries.
  Would it help if I added some info to the wiki page on how I think
  that a cache should work?

I'll follow up with a few further points in another e-mail.

                               Peter

=2D-=20
Dr Peter Brett <peter AT peter-b DOT co DOT uk>

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iEYEARECAAYFAlIurkcACgkQZ7Gbq7g7vpq+nQCePMmPh1If8TmghTOvjKmlaapi
84YAnjIA1BdJ79PD6tO6hnPT3zjzJiLi
=iYre
-----END PGP SIGNATURE-----
--=-=-=--