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=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type:content-transfer-encoding;
	bh=DkKpjcm3zvGm5LHfIRsqdU0Yto5pwJhN3qktsAZvHI0=;
	b=sGduoT4eahSUVdiuqznIMOpeO1qbq3eitjFYlw7VacxAoY+xGrxTcCRXzjy2cLgd8a
	JDKk55hA/mKQD+4tT1O73hBl9hJUhXkbRdctw8nNA6yB2dv/BBhlp+SGFGr73mpOmGkW
	CMJZOISA91ClKYgXMGrMLZzMXAo1BvcZTaazVrBpR3jfyKtZDOsUqQpTqFhrUIwJEEk/
	zVkN9OucEOt8JdAakxbnUXexmhJakyD/t2aqTbuAVXk5cX9Lk22VM4CmeNe0fT0PqGBG
	VjB83/BPT9zs8QKGKLoN4cN2rA6N4TcCfJk/lQoGxd14FMu96fCIrywYyfsxtZrbRjCx
	LODA==
MIME-Version:	1.0
X-Received:	by 10.112.198.198 with SMTP id je6mr375563lbc.31.1444794400180;
	Tue, 13 Oct 2015 20:46:40 -0700 (PDT)
In-Reply-To:	<38EA4E25-A99C-4732-B803-215D5FCC3264@noqsi.com>
References:	<1042003D-82E2-40F0-AB60-8186580C46AD AT noqsi DOT com>
	<201510121905 DOT t9CJ5T9W026297 AT envy DOT delorie DOT com>
	<CAM2RGhTMnybSnYgnNhVZGA6PTvyJu+=Kzd5LX2HMqxT1F4LoRg AT mail DOT gmail DOT com>
	<88EA58F5-2B23-498A-9E5B-84054976DBED AT noqsi DOT com>
	<CAM2RGhTPPtqmWVa3=Kf-PeN+WS5Tn4J+D0Ri6R_4OrQOk+LFKQ AT mail DOT gmail DOT com>
	<4D3CD563-D8EE-4B2A-975A-AC2B573960FF AT noqsi DOT com>
	<CAM2RGhT8WzhwvzFx3Rfv8vN-f=i1=uWuLF+48VygSRtfdzdo-A AT mail DOT gmail DOT com>
	<34B17816-9EA5-45FD-BFB4-9D623A8D3D87 AT noqsi DOT com>
	<CAM2RGhR+K+dvDdXsbk0Y6LN=-7RhhG5wvtG4i0k4+uMgzd=H0w AT mail DOT gmail DOT com>
	<39FF6208-7D45-4DE8-9AEE-1ED1B512705B AT noqsi DOT com>
	<CAM2RGhROpz_3y2JB=xEkEQ3CMHqHJ_WZxqVrbQhP4q2mg40h8g AT mail DOT gmail DOT com>
	<C8AC7729-F0BC-4CFA-95DA-65CCEF10EC4E AT noqsi DOT com>
	<201510140229 DOT t9E2T45e021346 AT envy DOT delorie DOT com>
	<B4A88DFF-97D8-4391-9BC6-E4EA2EF4D69B AT noqsi DOT com>
	<CAM2RGhQCsY9+bKRtHYXTt_UTNzAMEa6em8HzLtB0oy6rMdhiAA AT mail DOT gmail DOT com>
	<38EA4E25-A99C-4732-B803-215D5FCC3264 AT noqsi DOT com>
Date:	Wed, 14 Oct 2015 03:46:40 +0000
Message-ID:	<CAM2RGhRVG81aPnppn-38R_HHx_P97wpA1FiFkb9GYVYOw1=akQ@mail.gmail.com>
Subject:	Re: [geda-user] A lesson from gnet-makefile
From:	"Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	gEDA users mailing list <geda-user AT delorie DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t9E3ki2L032714
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

On Wed, Oct 14, 2015 at 3:26 AM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Oct 13, 2015, at 8:56 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
>> On Wed, Oct 14, 2015 at 2:47 AM, John Doty <jpd AT noqsi DOT com> wrote:
>>>
>>> On Oct 13, 2015, at 8:29 PM, DJ Delorie <dj AT delorie DOT com> wrote:
>>>
>>>>
>>>>> No, I assume that you don't know what might break the tools.
>>>>
>>>> Please don't assume the worst of people.
>>>>
>>>
>>> I don’t. I do assume that good people will make blunders. This is completely normal. I’ve made enough of them. Minimizing the opportunities for blunders is important.
>>
>> Yet you talk like it would doom the suite when in reality it could
>> just be fixed.
>
> Would it be? The current developer culture is so pcb-centric I have no confidence that anyone would care.

Yes and I have sided with you on that as I said before often in a
minority of 2 or 3 people.
Ultimately you have to trust people and the community or have your own
fork. Although as the only person who is actively writing gnetlist
backends you basically already have that.

>>
>> Old workflows using the flat nets already have userbase that gets
>> priority in conflicts.
>
> I’m all for hierarchical netlisting. Maybe you should look at how gnet-spice-noqsi (https://github.com/noqsi/gnet-spice-noqsi) or Paul Tan’s hierarchical Verilog netlisting approach (see his posts on this list from a few years ago) gets it done. No need for major surgical intervention.

I don't see what these how these two sentences are negating any of my
points. If anything they prove that other people are still free to
implement their workflows as they see fit at a higher level.

"surgical intervention" dude way to much rhetoric here.

>> The new nets have no users and we can change
>> them after an unstable release with out harming anyone's work. I
>> thought that was the point of unstable releases, branches and etc.
>
> It’s even more the point of new tools and scripts.

True but this is a functionality that should be available everywhere
s_conn is. A point you really have yet to produce a good counter
argument too.

>>
>>> John Doty              Noqsi Aerospace, Ltd.
>>> http://www.noqsi.com/
>>> jpd AT noqsi DOT com
>>>
>>>
>>
>>
>>
>> --
>> Home
>> http://evanfoss.googlepages.com/
>> Work
>> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/
>>
>>
>
> John Doty              Noqsi Aerospace, Ltd.
> http://www.noqsi.com/
> jpd AT noqsi DOT com
>
>



-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/

- Raw text -