X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Mon, 13 Feb 2017 19:56:08 +0000
From: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Experimental branch using xorn
Message-ID: <20170213195608.GI21523@foo.stuge.se>
References: <CAJXU7q-VqAGYeheVBON8+TdwsM84rq1z2bKoi_S-0Sax49W-Zw AT mail DOT gmail DOT com>
 <20170211174559 DOT GM21523 AT foo DOT stuge DOT se>
 <CAJXU7q_h9+g4FzQYGH1xgUzJtG=++fFgeA851DVX2b5xo9zM8A AT mail DOT gmail DOT com>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1702120926470 DOT 7286 AT igor2priv>
 <alpine DOT DEB DOT 2 DOT 11 DOT 1702121041390 DOT 2050 AT nimbus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.11.1702121041390.2050@nimbus>
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

Roland Lutz wrote:
> Take for example the experimental branch I posted some time ago which 
> implements some netlister features which have been on the wishlist for 
> quite some time: working buses, parametric subschematics, and customizable 
> power symbols without a trailing ":1".  For every one of these features, 
> people have criticized me for not implementing it their own way:

I would recommend to consider the criticism, but take it with a good grain
of salt unless it is backed by something more than just personal preference.


> So I basically have the options to either merge my patches even though 
> there are people opposing them

Please go ahead and do just that.

By all means solicit review, maybe post some key patches to the
(developer) list, but don't accept random (as opposed to well-founded)
preferences as blockers if you disagree and have a better plan.

I certainly support migrating existing gEDA tools to use xorn C code.

I think limited breakage is acceptable during development if it can't
be avoided, but not for a release. And of course it's better if it
can be avoided. :)


//Peter