X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Qifuix5OK1VQblUxdiViUiuOPF3QHAqYeDPq4O2mghI=; b=IHAgXBHQxgz1l1/2vs7RmFofrqX37OpLfanwrKtQN/yXvwB0ERXP1Y1EgvR8xX/CgE rJr1ta0iyl3FJSClqZhXGQtDNvM142CIfhavkMjHDOKUDP4jXRvGIOzSRkKBolDaNduf bzCsY9lkjFR2rjwYh72+lpHIfonY6x/01/AjlHCUt7MpfqnYvBZhfhJr9NhKG1PYVPtz bV8mytjTs91UxiRGH4FShU4eYJI6mkes3Ir0yKxc0c9t+ZFvC7YWVFWHIURix2VuVXm8 01ZQU6MXppHwdjiAU1SxRk6vA8RmGtpmYddwqTnuglGSi5Vpd4VJFPGegII8KANs55m5 ZULw== MIME-Version: 1.0 X-Received: by 10.50.23.76 with SMTP id k12mr1174170igf.37.1378951997351; Wed, 11 Sep 2013 19:13:17 -0700 (PDT) In-Reply-To: <522F5916.5070008@sbcglobal.net> References: <87ob83dodl DOT fsf AT harrington DOT peter-b DOT co DOT uk> <87sixdi6rc DOT fsf AT harrington DOT peter-b DOT co DOT uk> <522F5916 DOT 5070008 AT sbcglobal DOT net> Date: Wed, 11 Sep 2013 18:13:17 -0800 Message-ID: Subject: Re: [geda-user] [RFC] Major changes to symbol/schematic libraries in geda-gaf From: Britton Kerin To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=089e0158a9b6f70b5304e62647b0 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 --089e0158a9b6f70b5304e62647b0 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 10, 2013 at 9:38 AM, Girvin Herr wrote: > Peter et al, > I certainly hope that whatever you change, still transparently allows the > use of the current (old) symbols in gschem. If it does not, then that will > break a ton of my schematics, which is not very friendly. I tried > embedding symbols in my schematics a while back, which was not entirely > successful. IIRC, it had to do with copying the embedded symbols. As a > result, all of my schematics reference my external library, which is > populated with my own symbols as well as symbols copied from the standard > gschem library and modified. I would not be pleased if this connection > were broken in 1.9.x and I get a slew of red triangles in my schematics. > In fact, by the standard software development versioning rules, if the API > changes, the major version number should change. i.e. 1.9.x should be 2.x. > Girvin Herr > Exactly the same situation here. Britton --089e0158a9b6f70b5304e62647b0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Tue, Sep 10, 2013 at 9:38 AM, Girvin Herr <girvin DOT herr AT sbcg= lobal.net> wrote:
Peter et al,
I certainly hope that whatever you change, still transparently allows the u= se of the current (old) symbols in gschem. =A0If it does not, then that wil= l break a ton of my schematics, which is not very friendly. =A0I tried embe= dding symbols in my schematics a while back, which was not entirely success= ful. =A0IIRC, it had to do with copying the embedded symbols. =A0As a resul= t, all of my schematics reference my external library, which is populated w= ith my own symbols as well as symbols copied from the standard gschem libra= ry and modified. =A0I would not be pleased if this connection were broken i= n 1.9.x and I get a slew of red triangles in my schematics. =A0In fact, by = the standard software development versioning rules, if the API changes, the= major version number should change. =A0i.e. =A01.9.x should be 2.x.
Girvin Herr


Exactly the same = situation here.

Britton
=A0

--089e0158a9b6f70b5304e62647b0--