X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Mailer: exmh version 2.8.0 04/21/2012 (debian 1:2.8.0~rc1-2) with nmh-1.5
X-Exmh-Isig-CompType: repl
X-Exmh-Isig-Folder: inbox
From: karl AT aspodata DOT se
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] identical symbol names
In-reply-to: <CAG4ve9+QsUf=nVXPe-f3VddGiqHn8sjZUJNkdu3QV1cOQDWiAg@mail.gmail.com>
References: <CAG4ve9LgHNoVZoGaGgF67tadJ_n=L6Uy1g=UPPrkM0fL6Rgufw AT mail DOT gmail DOT com> <20140127234944 DOT 924148045B78 AT turkos DOT aspodata DOT se> <CAG4ve9+3jhFJ1Cr6CLUyLX_y02uigJECiUCwxjUWdP=heVocqg AT mail DOT gmail DOT com> <20140128201110 DOT DF7D78045B78 AT turkos DOT aspodata DOT se> <20140129072550 DOT GA24560 AT localhost DOT localdomain> <CAG4ve9+v9QxNRaPSFkmGfr6bKsv7km-Gt_gwXF7Eh4TX+AmNug AT mail DOT gmail DOT com> <CAOP4iL2JBUdF93kZF-iQ9Rv+VTN3iXoT+6C4LoBi5qaMxof=sA AT mail DOT gmail DOT com> <CAG4ve9+QsUf=nVXPe-f3VddGiqHn8sjZUJNkdu3QV1cOQDWiAg AT mail DOT gmail DOT com>
Comments: In-reply-to =?KOI8-R?B?4czFy9PFyiDowdLYy8/X08vJyg==?= <svetonomer AT gmail DOT com>
   message dated "Sun, 09 Mar 2014 00:57:49 +0400."
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Message-Id: <20140309173951.738798020179@turkos.aspodata.se>
Date: Sun,  9 Mar 2014 18:39:51 +0100 (CET)
X-Virus-Scanned: ClamAV using ClamSMTP
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

svetonomer AT gmail DOT com:
> John Eaton:
> > If we add that information to the .sch then you will be able to tell it
> > apart from all of the other components with the same name.
> 
> Yes it is. This will work too.
> But why memorize a path that may change someday.
> And the project will be damaged.
> 
> In addition all computers the project will be developed the same way should
> be for included libraries.
> 
> > And while we are at it we should also add fields for revision and variant.
> > They will come in handy.
> >
> 
> You can go this way, but it will be a crutch.
> Case proposed by me makes schematic files self-sufficient.

The file format only contains the basename (e.g. triac-1.sym). That is 
the root of the problem. As you can see below, the basename is really 
insufficient:

$ find cvs.gedasymbols.org/ -type f -name \*.sym | sed -e 's/.*\///;' | sort | uniq -c | sort -n -r | head
      4 out.sym
      4 led.sym
      4 in.sym
      4 gnd-1.sym
      3 Ub+.sym
      3 triac-1.sym
      3 title-block.sym
      3 switch-pb.sym
      3 Si9948AEY.sym
      3 opamp.sym
$

One solution is to use your patch and another is to copy the relevant 
sym's to the project directory, possible renaming the files at the same 
time.

But there will be a lot of copying, where I would like it to be 
refencing instead, so I have to side with John. We have to come
up with something more and the version thing is on the list --
if you are using symbols from the cvs (cvs.gedasymbols.org) you'll
will notice that from time to time (by using cvs -q update -dP)
the symbols will change, dissapear, or move to another directory,
so you need the version thing. Even if you maintain symbols in your
own repository, you sometimes need to update a symbols due to
for some reason, and then you have the same situation.

Also, most(?) geda devs seems to like scheme code instead of c, so
if you come up with some scheme code you'll probably have a greater
chance that your patch will be applied.

///

So what is on the whishlist?

A start might be, to be able to handle:
. cvs/svn/git/hg/... repositories
. local or remote (possible caching the remote symbols)
. duplicate filenames

Any more ?

Regards,
/Karl Hammar

-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57