delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2015/04/02/11:03:12

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=rezFBPeQ66o5I/Y3y7R643TsCCmnWYqC3CP33z61YA4=;
b=j7Dqf3tEu58EK5MPu/atn9SPLBe5sFSjhBymUR5qQVNWKP4ThzMxvo34XfbOVoWsjG
RRUKNNplDVcgaGP9dZTDOk210bbEvZ/r5U+LVICD6MbbmnVmCENifdUhDs6Gdeyvahnq
kGTlFy0aHNR1OCPkobuFda6WcBltBrIb5jbe+CNEwGN8UVZP4OdykEYn3nYV+lWf3keg
TQaFjDhVHmsa486CqGccgNhxwjEqRzkBoR2j0EOX3j+K4qEi16ZF5rS92bjEbnC/PLc8
bt+tWtyd2lp2TGmKuPit0W74j/5vCEGKQbfrz9r0syUI80pU4xS4tyW+RL2Ik4FhUA8Z
vVGw==
MIME-Version: 1.0
X-Received: by 10.107.169.35 with SMTP id s35mr72028597ioe.46.1427986947606;
Thu, 02 Apr 2015 08:02:27 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1504020454050.25799@igor2priv>
References: <1427905808 DOT 32608 DOT 60 DOT camel AT benjamin-hp-g70>
<20150401214846 DOT 5d2261e6 AT jive>
<201504011954 DOT t31JsnKh020289 AT envy DOT delorie DOT com>
<20150401221210 DOT 1b4a299e AT jive>
<201504012014 DOT t31KEq1m020861 AT envy DOT delorie DOT com>
<551C574F DOT 2030708 AT xs4all DOT nl>
<CA+uY=MTgd=aS-vyUE8RHcHZr+dJjtBe_h4yAFANPi6VBPUPVhQ AT mail DOT gmail DOT com>
<alpine DOT DEB DOT 2 DOT 00 DOT 1504020454050 DOT 25799 AT igor2priv>
Date: Thu, 2 Apr 2015 11:02:27 -0400
Message-ID: <CA+uY=MT=Td=0VMgHfRcQtuYYTx7v8YVNCmFPn353Liki9QTTSQ@mail.gmail.com>
Subject: Re: [geda-user] PCB and gschem libraries
From: Russell Nelson <russnelson AT gmail DOT com>
To: geda-user AT delorie DOT com
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

--001a11421470c19a2a0512bf1eda
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 1, 2015 at 11:00 PM, <gedau AT igor2 DOT repo DOT hu> wrote:

>
>
> On Wed, 1 Apr 2015, Russell Nelson wrote:
>
>  IMHO, the gedasymbols library is fine. If it were easier to use, people
>> would use it more. Here is what I suggest:  o Take the current set of
>> symbols and footprints and incorporate them into gedasymbols.
>>   o Nuke the current set of symbols and footprints.
>>   o Replace it by a cached copy of gedasymbols.
>>   o Make it easy to refresh the cached copy using, say, rsync or somesuch.
>>   o ONLY, and I mean ONLY pull footprints out of the cached copy.
>>
>> In other words, when you create a footprint or symbol, the only way to use
>> it is to pull it out of gedasymbols. So when you create a symbol or
>> footprint, you can simultaneously creating it on gedasymbols. If you
>> happen
>> to be offline, well, you can pull it out of your cached copy. But when you
>> refresh, the refresh works bidirectionally. Everything you've created
>> becomes available to everyone else.
>>
>
> Would be the moment I had to fork gschem and rest of geda as well. I
> simply don't believe in such centralized/cloud "we tell you where and how
> to store your own stuff" methods. Some implications:
>
> 1. licenses: what if someone wants to have a symbol/fp lib that is not
> distributed or distributed under different conditions that's not applicable
> on gedasymbols? E.g. you are a small company trying to make proprietary
> design (contract work?) using open tools and for whatever legal reasons you
> are not allowed to share any parts of the design (including new
> symbols/fps).
>

You use GPL software. Why do you object to a GPL parts library?


> 2. sandbox: what if I want to have 200 variants of a symbol/fp for
> whatever experiment? Do I have to pollute the central library and everyone
> will always pull all them?
>

Yes. Some contributions would be worthless. Isn't that always going to be
the case?


> 3. in case you still allow local symbols of some sort: what if I have
> multiple systems I want to use my own local symbols on? I will use version
> control on them (just like now). What if a central symbol added later
> starts to collide with my own?
>

My proposal makes no allowance for local symbols. Isn't that clear enough?


> I think this kind of cloud approach would decrease usability/flexibility
> of the tools big times. This kind of thing is more appropriate to web based
> design tools.
>

So you don't use gedasymbols? You only use the symbols/footprints that
comes with gschem/pcb? Or else you create your own proprietary symbols and
never share them? Well then you would never sync with gedasymbols, so what
about this proposal is displeasing you?


> Regards,
>
> Igor2

--001a11421470c19a2a0512bf1eda
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 1, 2015 at 11:00 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:gedau=
@igor2.repo.hu" target=3D"_blank" onclick=3D"window.open(&#39;https://mail.=
google.com/mail/?view=3Dcm&amp;tf=3D1&amp;to=3Dgedau AT igor2 DOT repo DOT hu&amp;cc=
=3D&amp;bcc=3D&amp;su=3D&amp;body=3D&#39;,&#39;_blank&#39;);return false;">=
gedau AT igor2 DOT repo DOT hu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><span class=3D""><br>
<br>
On Wed, 1 Apr 2015, Russell Nelson wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
IMHO, the gedasymbols library is fine. If it were easier to use, people<br>
would use it more. Here is what I suggest:=C2=A0 o Take the current set of<=
br>
symbols and footprints and incorporate them into gedasymbols.<br>
=C2=A0 o Nuke the current set of symbols and footprints.<br>
=C2=A0 o Replace it by a cached copy of gedasymbols.<br>
=C2=A0 o Make it easy to refresh the cached copy using, say, rsync or somes=
uch.<br>
=C2=A0 o ONLY, and I mean ONLY pull footprints out of the cached copy.<br>
<br>
In other words, when you create a footprint or symbol, the only way to use<=
br>
it is to pull it out of gedasymbols. So when you create a symbol or<br>
footprint, you can simultaneously creating it on gedasymbols. If you happen=
<br>
to be offline, well, you can pull it out of your cached copy. But when you<=
br>
refresh, the refresh works bidirectionally. Everything you&#39;ve created<b=
r>
becomes available to everyone else.<br>
</blockquote>
<br></span>
Would be the moment I had to fork gschem and rest of geda as well. I simply=
 don&#39;t believe in such centralized/cloud &quot;we tell you where and ho=
w to store your own stuff&quot; methods. Some implications:<br>
<br>
1. licenses: what if someone wants to have a symbol/fp lib that is not dist=
ributed or distributed under different conditions that&#39;s not applicable=
 on gedasymbols? E.g. you are a small company trying to make proprietary de=
sign (contract work?) using open tools and for whatever legal reasons you a=
re not allowed to share any parts of the design (including new symbols/fps)=
.<br></blockquote><div><br></div><div>You use GPL software. Why do you obje=
ct to a GPL parts library?</div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
2. sandbox: what if I want to have 200 variants of a symbol/fp for whatever=
 experiment? Do I have to pollute the central library and everyone will alw=
ays pull all them?<br></blockquote><div><br></div><div>Yes. Some contributi=
ons would be worthless. Isn&#39;t that always going to be the case?</div><d=
iv>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
3. in case you still allow local symbols of some sort: what if I have multi=
ple systems I want to use my own local symbols on? I will use version contr=
ol on them (just like now). What if a central symbol added later starts to =
collide with my own?<br></blockquote><div><br></div><div>My proposal makes =
no allowance for local symbols. Isn&#39;t that clear enough?</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
I think this kind of cloud approach would decrease usability/flexibility of=
 the tools big times. This kind of thing is more appropriate to web based d=
esign tools.<br></blockquote><div><br></div><div>So you don&#39;t use gedas=
ymbols? You only use the symbols/footprints that comes with gschem/pcb? Or =
else you create your own proprietary symbols and never share them? Well the=
n you would never sync with gedasymbols, so what about this proposal is dis=
pleasing you?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Regards,<br>
<br>
Igor2</blockquote></div><br></div></div>

--001a11421470c19a2a0512bf1eda--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019