X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<1473889184.5243.51.camel@oscopy.org>
Subject:	Re: [geda-user] Oscopy
From:	Arnaud Gardelein <arnaud AT oscopy DOT org>
To:	geda-user AT delorie DOT com
Date:	Wed, 14 Sep 2016 23:39:44 +0200
In-Reply-To:	<20160903111351.GA32623@localhost.localdomain>
References:
	<CANqhZFwC48g07MUY411a20C5oipkmmkzUimhz8OgvL2Thi-yDg AT mail DOT gmail DOT com>
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

 <1471984429 DOT 18763 DOT 30 DOT camel AT oscopy DOT org>
	 <20160903111351 DOT GA32623 AT localhost DOT localdomain>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.20.3-1 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u8ELjDGx011139

Le samedi 03 septembre 2016 à 14:13 +0300, Vladimir Zhbanov
(vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com] a écrit :
> On Tue, Aug 23, 2016 at 10:33:49PM +0200, Arnaud Gardelein wrote:
> ...
> > > To select which version of oscopy.scm to use, I was wondering
> > whether
> > it could be performed either at install time of at execution time.
> 
> You could use any one of the strategies.
> 
> > Would there be a way to get the gschem version ? It seems that
> > gschem
> > does not implement the command line option like '--version'. If
> > needed
> > I could submit a patch to implement this option.
> 
> $ gschem --version
> gEDA 1.9.2 (gc48c185)
> Copyright (C) 1998-2012 gEDA developers
> Это свободное программное обеспечение, и его можно распространять при
> определённых условиях. Подробности см. в файле COPYING
> в дистрибутиве gEDA.
> Нет НИКАКИХ ГАРАНТИЙ в рамках, допустимых имеющимся
> законодательством.
> 
> Probably I don't understand what you are meaning here (?).
> 
My mistake. I was confused by an ancient version (1.6.0) installed a
long time ago on my machine in parallel of the recent one. Thanks to a
wrong $PATH setting when checking for '--version' it used this one and
not the default.

> Moreover, there is the scheme procedure `gschem-version', which
> though works not as I would expect. Comments in the sources say:
> --------------------------------8<--------------------------------
> /*! \brief Verify the version of the RC file under evaluation.
>  *  \par Function Description
>  *
>  *  Implements the Scheme function "gschem-version". Tests the
> version
>  *  string in the argument against the version of the application
>  *  itself.
>  *
>  *  \param [in] scm_version Scheme object containing RC file version
> string
>  *
>  *  \returns #t if the version of the RC file matches the
> application,
>  *           else #f.
>  */
> -------------------------------->8--------------------------------
> 
> I tried it against the version specified in my system-gschemrc and
> it works as above:
> 
> scheme@(guile-user)> (gschem-version "20150930")
> $8 = #t
> scheme@(guile-user)> (gschem-version "xxx")
> $9 = #f
> 
> The only thing you would need is to know actual release dates ;-)
I've pushed to experimental an attempt to detect at oscopy.scm startup
the actual version of gschem. I'm not sure this is an elegant way to do
it. For now it "works for me".

> > Eventually I fixed the communication between gschem and oscopy. I
> > took
> > me some time to figure out how to activate actions from gschem, as
> > dbus-send do not support complex datasets. I was not able to find
> > suitable DBus bindings with Guile, although it seems that Chicken
> > has
> > [2]. Maybe someone here could point me to the right direction ?
> 
> The only non-ancient thing I found so far is [1] (found in the
> discussion at [2]).
I'll have a look at it. Thanks.

Arnaud.

- Raw text -