X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 173.48.170.224 X-Authenticated-UID: jpd AT noqsi DOT com From: John Doty Content-Type: multipart/alternative; boundary="Apple-Mail=_3338C1A7-BC50-4263-8F8E-EB6CA5EC3DEC" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [geda-user] Refdes bug or Master Attribute Document on the Wiki needs update. Date: Wed, 30 Jan 2019 10:12:02 -0500 References: <9ed059c0-f3c5-1482-169b-f8f1119f3208 AT fastmail DOT com> To: geda-user AT delorie DOT com In-Reply-To: Message-Id: <5BC4365D-FBD0-4495-806B-C30BA710D31B@noqsi.com> X-Mailer: Apple Mail (2.3273) 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 --Apple-Mail=_3338C1A7-BC50-4263-8F8E-EB6CA5EC3DEC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jan 30, 2019, at 8:27 AM, Roland Lutz wrote: >=20 > I always wondered about this mechanic. As far as gEDA/gaf is = concerned, only components which share a common refdes are part of one = package, so U1a, U1b etc. are individual packages. Any logic that = deviates from this would be specific to PCB and/or gsch2pcb. Remember, pcb existed before gEDA, and Ales designed gEDA to support = *any* downstream flow, not just pcb. This is a place where core gEDA = conventions don=E2=80=99t quite match the conventions of the downstream = tool. For other flows, the back end manages the mismatch, sometimes with = the help of additional attributes. For example, the =E2=80=9Cpins=E2=80=9D= attribute in some library symbols is there to support Allegro. The pcb = flow didn=E2=80=99t get this kind of attention. It appears that nobody = on the gEDA side anticipated the situation where pcb would become the = most popular downstream tool, and nobody on the pcb side wanted to step = up and do the Scheme coding at the interface. So, we have a three way fork, with pcb-rnd centered on repairing the = architecture of pcb, but with its own schematic capture, and gEDA = becoming a pcb-centric tool, no longer much of a kit. Neither of these = forks seems focused on maintaining the flexibility of gEDA as a primary = goal: Lepton is keeping that dream alive. John Doty Noqsi Aerospace, Ltd. jpd AT noqsi DOT com --Apple-Mail=_3338C1A7-BC50-4263-8F8E-EB6CA5EC3DEC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Jan 30, 2019, at 8:27 AM, Roland Lutz <rlutz AT hedmen DOT org> = wrote:

I always wondered about this = mechanic. As far as gEDA/gaf is concerned, only components which = share a common refdes are part of one package, so U1a, U1b etc. are = individual packages. Any logic that deviates from this would be = specific to PCB and/or gsch2pcb.

Remember, pcb existed before gEDA, and Ales = designed gEDA to support *any* downstream flow, not just pcb. This is a = place where core gEDA conventions don=E2=80=99t quite match the = conventions of the downstream tool. For other flows, the back end = manages the mismatch, sometimes with the help of additional attributes. = For example, the =E2=80=9Cpins=E2=80=9D attribute in some library = symbols is there to support Allegro. The pcb flow didn=E2=80=99t get = this kind of attention. It appears that nobody on the gEDA side = anticipated the situation where pcb would become the most popular = downstream tool, and nobody on the pcb side wanted to step up and do the = Scheme coding at the interface.

So, we have a three way fork, with pcb-rnd centered on = repairing the architecture of pcb, but with its own schematic capture, = and gEDA becoming a pcb-centric tool, no longer much of a kit. Neither = of these forks seems focused on maintaining the flexibility of gEDA as a = primary goal: Lepton is keeping that dream alive.

John Doty = Noqsi = Aerospace, Ltd.

jpd AT noqsi DOT com

= --Apple-Mail=_3338C1A7-BC50-4263-8F8E-EB6CA5EC3DEC--