X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
From: geda AT psjt DOT org (Stephan =?utf-8?Q?B=C3=B6ttcher?=)
To: "Svenn Are Bjerkem \(svenn.bjerkem\@googlemail.com\) \[via geda-user\@delorie.com\]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] New gEDA/gaf features
References: <alpine DOT DEB DOT 2 DOT 11 DOT 1702141710390 DOT 14019 AT nimbus>
	<s6nefz0a72x DOT fsf AT blaulicht DOT dmz DOT brux>
	<CAGde_xNi3Yt3fDz=uGiR2M740eObKsJ9fyzZRPmk-MsQ2z20jQ AT mail DOT gmail DOT com>
Date: Tue, 14 Feb 2017 23:34:01 +0100
In-Reply-To: <CAGde_xNi3Yt3fDz=uGiR2M740eObKsJ9fyzZRPmk-MsQ2z20jQ@mail.gmail.com>
	(Svenn Are Bjerkem's message of "Tue, 14 Feb 2017 22:45:38 +0100")
Message-ID: <s6ny3x88krq.fsf@blaulicht.dmz.brux>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id v1EMYA8c029964
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

"Svenn Are Bjerkem (svenn DOT bjerkem AT googlemail DOT com) [via
geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> writes:

> On 14 February 2017 at 20:46, Stephan Böttcher <geda AT psjt DOT org> wrote:
>> Roland Lutz <rlutz AT hedmen DOT org> writes:
>>
>>> as I pointed out in the the other thread[1], I just merged a few new
>>> features into gEDA/gaf master.  In order to use them, you need to
>>> build the current development version of gEDA/gaf from the
>>> repository.[2]
>>
>> Maybe I am confused, please help me understand.
>>
>> When I pull and build git://git.geda-project.org/geda-gaf, I will now
>> get gschem and gnetlist from Roland, with the new xorn/python machinery
>> underneath?
>
> You will get gschem the way it is currently handled by Roland.

It looks like the old gnetlist is still in there, my patches apply
cleanly.  And I get:

$ gnetlist
*** The new netlister frontend has been disabled during configuration. ***
*** If you want to use the lecagy frontend instead, you can select it  ***
*** by adding (set! use-legacy-frontend #t) to your gnetlistrc file.   ***

Sad.

>> When I pull from Vladimir's fork (where is that?) I will get something
>> where a lot of C has be reimplemented in scheme?
>
> git remote add vzh http://github.com/vzh/geda-gaf.git
> git fetch --all
> gitk --all

Thanks!

>> I guess I will need on use my own fork for a while, which so far used to
>> be git://git.geda-project.org/geda-gaf master with this patch:
>> https://bugs.launchpad.net/geda/+bug/911440.   I will need to find some
>> commit in master to use for this purpose.  Good opportunity to learn some
>> more git.
>
> When you have both mainline (Roland) and vzh (Vladimir) in your local
> working git area, you can try to rebase your patch to either and see
> how far you get in time before the rebase need some help to get to the
> tip of each fork.

>> Maybe, when there is a clear cut between projects, I may test out the
>> new stuff, but not anytime soon.
>
> the clear cut 

I meant to say "a clear cut in my own projects".  I have a tree of
schematics and layouts, with reused sub-schematics all over, and I do
not want to risk breaking stuff by trying a new netlister.

> so far came on d9e2745fdb7214491c44abdd3dd86ff2a9ee937f when Vladimir
> removed xorn in his vzh branch on github.  For quite some time there
> was no action in mainline (Roland), but now things are happening there
> too.
>
>>
>> This is all very sad.
>
> It is unfortunate that things happen in master. There should be more
> active use of feature branches in order to give people possibility to
> have a slight more stable master to use when building from source, and
> to test the features for possible unintended breakage.
>
> One way is to use git fetch and then gitk to inspect what has happened
> instead of diving heads-in with git pull
> And set a local tags on commits that happen to suit your needs.

See, I am learning git fu right here :-) Thanks.

-- 
Stephan