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=McPoGTtLPGujCKBrFsy6ye4RThT+VwtVHnd10rWsPF0=; b=x6nF6bQ+fZcICer0vG2YwrwC9kbu2ElmKGfD0qS6sAX/uBhwCxMlWUNfoQ5oDZdpvv gMShcppp6QMPzWcxJOkDqWrf8xuGzcC3eoG4egcPpA+CIGmAgNHCJbhNnD0R66Xv7Emt Ziuvqzb6zsElj6Vp0De5lkOuNTK4zXBxeOag27heYgAsq8e24qd4n5tQ222owGm4TalK cTjJLXr/GZJ7Cn2Rmtj4WaxkHMz9qeHIzlIb65MNmTypqOdh0HVA0xsrlEdZ8jQbKnnE 2F2ZJjUB1kjvL1VjJLrPtg87C71AsQWeshT21RuO7b2CuVz1J3bb4YKvDeJP+NeWqeMD HaQA== MIME-Version: 1.0 In-Reply-To: <20121028164801.GA4859@alpha2> References: <6BF2E986-51EB-41E9-A4AD-8071CD00B1A1 AT jump-ing DOT de> <834283D4-0891-486E-A981-2FF20B32C615 AT noqsi DOT com> <54CAA7EE-7638-4B89-8197-111D0493F859 AT noqsi DOT com> <508CE947 DOT 4050408 AT xs4all DOT nl> <508D302D DOT 1030105 AT jump-ing DOT de> <20121028164801 DOT GA4859 AT alpha2> Date: Sun, 28 Oct 2012 20:54:40 +0100 Message-ID: Subject: Re: [geda-user] The state of gEDA/gaf (Was gEDA/PCBs diversity, Was: Pin hole size) From: Svenn Are Bjerkem To: geda-user AT delorie DOT com Content-Type: text/plain; charset=ISO-8859-1 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 On 28 October 2012 17:48, Ivan Stankovic wrote: > Right. Big projects need flexibility that only gEDA can provide and the > users are accustomed to its configuration. Since, as everyone knows, the > best way to extend or configure gEDA is by using a C compiler, the fact > that there are so many gEDA forks out there is a clear testament of the > toolkit's adoption and strengths. I am looking for those gEDA forks for my own interest. I found the ones on github and Bernd Jendrissek's on repo.or.cz. In the forks I have found so far, only Bernd's is diverging so much from the original code base that it can really be called a fork. (Like when inkscape forked from sodipodi and became what it is today.) The github stuff seems more like feature branches where the best stuff get merged back. If a fork changed name, to reflect its strive for individuality, I have not yet found them, and would be happy to learn their location. I think I am most interested in the parts up and until the end of gnetlist, that is, all the stuff which lead to a netlist output. -- Svenn