Mail Archives: geda-user/2017/02/15/17:59:00
--Apple-Mail=_58C1D7BE-EF81-4FF8-8FEA-E33EEA5D4210
Content-Type: multipart/alternative;
boundary="Apple-Mail=_83E3DDAD-1BA4-4143-A06F-943332DAFF5F"
--Apple-Mail=_83E3DDAD-1BA4-4143-A06F-943332DAFF5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
On Feb 15, 2017, at 3:31 PM, Peter Clifton =
(petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] =
<geda-user AT delorie DOT com> wrote:
>=20
>=20
> On 15 Feb 2017 22:14, "Roland Lutz" <rlutz AT hedmen DOT org> wrote
>=20
> The pcbfwd backend works with the current version of gEDA/gaf, as =
should any other backend, shipped or not. The breakage we talked about =
was related to a backend which required a patched gnetlist binary, =
something which should be avoided if possible. I think that if there is =
any consequence from this, it is that we should more actively include =
contributed backends into the main gEDA/gaf repository and add them to =
the regular test suite.
>=20
> The whole point of that backend is that it is shipped with pcb, and =
can be updated as pcb needs change from version to version.
>=20
> It implicitly relies (of course), on the netlister API being =
relatively stable, which had in the past been long standing geda policy.
>=20
> You'd need to go to Bert (pcb project lead) for the official answer, =
but I suspect out position here is "please don't" pull this particular =
netlist backend "upstream" to geda, since it lives in pcb.
I think it makes excellent sense to test gnetlist against every third =
party back end the developers can find. Distribution, on the other hand, =
is a separate issue, to be decided in individual cases.
>=20
> Peter
>=20
>=20
>=20
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_83E3DDAD-1BA4-4143-A06F-943332DAFF5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Feb 15, 2017, at 3:31 PM, Peter =
Clifton (<a =
href=3D"mailto:petercjclifton AT googlemail DOT com">petercjclifton AT googlemail DOT co=
m</a>) [via <a =
href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] <<a =
href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"auto"><br><div class=3D"gmail_extra" =
dir=3D"auto"><br><div class=3D"gmail_quote">On 15 Feb 2017 22:14, =
"Roland Lutz" <<a =
href=3D"mailto:rlutz AT hedmen DOT org">rlutz AT hedmen DOT org</a>> =
wrote<blockquote class=3D"quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
class=3D"quoted-text">
<br></div>
The pcbfwd backend works with the current version of gEDA/gaf, as should =
any other backend, shipped or not. The breakage we talked about =
was related to a backend which required a patched gnetlist binary, =
something which should be avoided if possible. I think that if =
there is any consequence from this, it is that we should more actively =
include contributed backends into the main gEDA/gaf repository and add =
them to the regular test suite.<br></blockquote></div></div><div =
dir=3D"auto"><br></div><div dir=3D"auto">The whole point of that backend =
is that it is shipped with pcb, and can be updated as pcb needs change =
from version to version.</div><div dir=3D"auto"><br></div><div =
dir=3D"auto">It implicitly relies (of course), on the netlister API =
being relatively stable, which had in the past been long standing geda =
policy.</div><div dir=3D"auto"><br></div><div dir=3D"auto">You'd need to =
go to Bert (pcb project lead) for the official answer, but I suspect out =
position here is "please don't" pull this particular netlist backend =
"upstream" to geda, since it lives in =
pcb.</div></div></blockquote><div><br></div>I think it makes excellent =
sense to test gnetlist against every third party back end the developers =
can find. Distribution, on the other hand, is a separate issue, to be =
decided in individual cases.</div><div><br><blockquote type=3D"cite"><div =
dir=3D"auto"><div dir=3D"auto"><br></div><div dir=3D"auto">Peter</div><div=
dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div =
dir=3D"auto"><br></div><div class=3D"gmail_extra" dir=3D"auto"><div =
class=3D"gmail_quote"><blockquote class=3D"quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div><br></div></div>
</blockquote></div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><p style=3D"margin: =
0.0px 0.0px 0.0px 0.0px"><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">John Doty<span =
class=3D"Apple-converted-space"> <span =
class=3D"Apple-converted-space"> </span><span =
class=3D"Apple-converted-tab"> <span =
class=3D"Apple-converted-space"> </span></span></span>Noqsi =
Aerospace, Ltd.</font></p><p style=3D"margin: 0.0px 0.0px 0.0px =
0.0px"><a href=3D"http://www.noqsi.com/">http://www.noqsi.com/</a></p><p =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><font face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica"><a =
href=3D"mailto:jpd AT noqsi DOT com">jpd AT noqsi DOT com</a></font></p><br =
class=3D"Apple-interchange-newline"></span>
</div>
<br></body></html>=
--Apple-Mail=_83E3DDAD-1BA4-4143-A06F-943332DAFF5F--
--Apple-Mail=_58C1D7BE-EF81-4FF8-8FEA-E33EEA5D4210
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJYpNyKAAoJEF1Aj/0UKykRByoQAJ2vGhO0gzKcC4hbCBWgYvds
MU/YnCedl5lZlnZ/NBeiowyz2/gQkDwVOc2JC6M5PUbE30xR0LH10IbgaND65CGr
oKNrSWHWL+1Ufnbvxnh6tWS8QfVRL2Yt2Y5EX5y/FBE/0t9Uex5ehEjDMI5MbhsU
ZpKGNj3sI/ZGzB1eOFx0GTe+4Joj6etGy+Tr9+yBJdJCgDfxlMa0h7Qe3uppb+at
0NrHIOTQMH1QUhY9j9ZF0LyOJS+rW1HzMn2FtWcesxaCTQ4HwbDnVOTgAsnV2Ypt
1rtbFkRIH/U7vL8g44nUfGstxPA6CrJY0SQW0MJlTwe9/Gh5V+41H8ZhWEYIMoRF
zvtR6K6MzJFVP4F1BUpTNidMoWYRDSavY7sYLnNUT/MJv1YbQ1LzxZuxDi6wPvSm
BGGbxFDbukCAoka3k1M/FeYrI/nrxqKA+q2bMLCqLo1v6wOKddXeBstBPxYE92C4
ZrwceUDvyFM64UvNlhqoNjZR1fuiMH8P9bAIFUI1iTHezd585HAfimhvbtMOBBGL
IT0KHJMo5Oq78Sk3lA5eqmojVpYqN7IIboGJOWtcTtpCKoD9IuWCBJEeFQ4x/CeH
pvT+CRSu3UQN7K0yaRBFq3k+qQ30rMTSIdqFYl8eZwIs+T4/v6ZalFboUmZtcawv
Jfzwyy0x/FbKQs+jSFHq
=HlEX
-----END PGP SIGNATURE-----
--Apple-Mail=_58C1D7BE-EF81-4FF8-8FEA-E33EEA5D4210--
- Raw text -