X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=uTvhC6toNCE5+JQnslVz7QnHaXHy0k02In3kvKlwzcw=; b=TunG2ZosZulYrKBufUNREkmQ51lLlpO278a0V96MCphRHagiWlVSTrGz7vRzV4iYes f668++TwEnqeS7WiAxPTQfzytsBTvovNDdCiCmrWbdH5jA1YuS4Aj2x7nXklNhZIMKnG fRmTQU1zf8IYmLmcSUzMoCwg0tOHkd4GTZMvOeCjER0VvteLFipwa1muMGdV0JBHuwZE O8osnsWWZYk6Yx8eFrmJB38AOHh65YCmV2oxuk4CUfGuzq/A7jRUYaz++Q5T+KB19jDz PvsGuqRRs2R/DYs0MHyLQWMYnnzXABQY6tGpcBg4n4S9fFPnzjRApIPuxXbDYmwQIBMN RMrw== X-Received: by 10.194.103.194 with SMTP id fy2mr1831853wjb.10.1444805259312; Tue, 13 Oct 2015 23:47:39 -0700 (PDT) Date: Wed, 14 Oct 2015 08:47:34 +0200 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] A lesson from gnet-makefile Message-Id: <20151014084734.47c681e21a7a6f2ab1a6b86f@gmail.com> In-Reply-To: References: <1042003D-82E2-40F0-AB60-8186580C46AD AT noqsi DOT com> <201510121905 DOT t9CJ5T9W026297 AT envy DOT delorie DOT com> <88EA58F5-2B23-498A-9E5B-84054976DBED AT noqsi DOT com> <4D3CD563-D8EE-4B2A-975A-AC2B573960FF AT noqsi DOT com> <34B17816-9EA5-45FD-BFB4-9D623A8D3D87 AT noqsi DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 > > Please not in libgeda or the geda-gaf core tools. That has tremendous potential to break things. geda-gaf is a mature toolkit in production use: changes to the core should not be taken lightly. New tools and new plug-ins are great. We have a transparent schematic format and powerful scripting mechanisms to give us power and to allow us to keep that power from interfering with each other’s objectives. > > We could prototype it via a plugin but in the long term it should > really be in the core. To be honest I find your "don't touch the core > you will break something" attitude kind of insulting. I am not out to > change how we have kept the concept of connections in libgeda and nets > in gnetlist. I just want to mirror the flat net model that already > exists in the core with a more nuanced and yet to be decided > structure. Yes if we want improvements we must accept changes which make it happen.