X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Thu, 2 Apr 2015 05:00:50 +0200 (CEST) X-X-Sender: igor2 AT igor2priv To: geda-user AT delorie DOT com X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: [geda-user] PCB and gschem libraries In-Reply-To: Message-ID: 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> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1717603964-1427943650=:25799" 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 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1717603964-1427943650=:25799 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE 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:=C2=A0 o Take the current set of >symbols and footprints and incorporate them into gedasymbols. >=C2=A0 o Nuke the current set of symbols and footprints. >=C2=A0 o Replace it by a cached copy of gedasymbols. >=C2=A0 o Make it easy to refresh the cached copy using, say, rsync or some= such. >=C2=A0 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 happe= n >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=20 simply don't believe in such centralized/cloud "we tell you where and=20 how to store your own stuff" methods. Some implications: 1. licenses: what if someone wants to have a symbol/fp lib that is not=20 distributed or distributed under different conditions that's not=20 applicable on gedasymbols? E.g. you are a small company trying to make=20 proprietary design (contract work?) using open tools and for whatever=20 legal reasons you are not allowed to share any parts of the design=20 (including new symbols/fps). 2. sandbox: what if I want to have 200 variants of a symbol/fp for=20 whatever experiment? Do I have to pollute the central library and everyone= =20 will always pull all them? 3. in case you still allow local symbols of some sort: what if I have=20 multiple systems I want to use my own local symbols on? I will use version= =20 control on them (just like now). What if a central symbol added later=20 starts to collide with my own? I think this kind of cloud approach would decrease usability/flexibility=20 of the tools big times. This kind of thing is more appropriate to web=20 based design tools. Regards, Igor2 --0-1717603964-1427943650=:25799--