modules and version numbers

modules and version numbers

[Marco Maggi]

Ciao,

  I am thinking about adding a version number to my modules;
I want  a simple scheme  'major.minor', with NO  patch level
and NO  status indicator  (devel, alpha, beta,  stable). The
major  number changes  only when  backward  compatibility is
broken.

  No  problem for C  language shared  libraries; so  far the
only  idea I  had  for Scheme  files  is to  call the  files
"./path/to/module-1.scm"  without minor  number in  the file
name, and so '(define-module (path to module-1))'.

  I wonder if someone had ideas about it.
Something that can be done now...

P.S.

  I have found:

http://lists.gnu.org/archive/html/guile-user/2005-09/msg00093.html

but  it is  not  available  now, nor  it  will be  available
anytime soon. And no, I cannot work on it.

--
Marco Maggi

"Now feel the funk blast!"
Rage Against the Machine - "Calm like a bomb"




_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user

Re: modules and version numbers

[Ludovic Courtès]

Hi Marco,

"Marco Maggi" <marco.maggi-ipsu@poste.it> writes:

>   No  problem for C  language shared  libraries; so  far the
> only  idea I  had  for Scheme  files  is to  call the  files
> "./path/to/module-1.scm"  without minor  number in  the file
> name, and so '(define-module (path to module-1))'. 

Looks like the best (the only?) short-term practical solution.

Thanks,
Ludovic.


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user

Re: modules and version numbers

[Andy Wingo]

Hi,

On Fri 05 Oct 2007 16:34, "Marco Maggi" <marco.maggi-ipsu@poste.it> writes:

> Ciao,
>
>   I am thinking about adding a version number to my modules;
> I want  a simple scheme  'major.minor', with NO  patch level
> and NO  status indicator  (devel, alpha, beta,  stable). The
> major  number changes  only when  backward  compatibility is
> broken. 

I documented the guile-gnome strategy here:

http://www.gnu.org/software/guile-gnome/docs/tutorial/getting-started/#getting-started

C libraries also encode the API version in their names (not sonames).

Regards,

Andy
-- 
http://wingolog.org/


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user

Re: modules and version numbers

[Marco Maggi]

"Andy Wingo" wrote:
>On Fri 05 Oct 2007 16:34, "Marco Maggi"
<marco.maggi-ipsu@poste.it> writes:
>>   I am thinking about adding a version number to my modules;
>I documented the guile-gnome strategy here:
>
>http://www.gnu.org/software/guile-gnome/docs/tutorial/getting-started/#getting-started

Thanks, special versioned modules are tempting... If I
allow parallel installations:

${sitedir}/gee/<full-version>/...
${sitedir}/gee/<other-full-version>/...

then there are two options:

* to use GUILE_LOAD_PATH explicitly
* to load first a special module (gee <full-version>)

then in each versioned module hierarchy I can have
(modname-1) and (modname-2) to support new
and old interfaces, or simply (modname).

I think that I can set up this installation layout
along with the special modules as a "configure"
option. It makes more difficult to write Autoconf
modules to be used in downstream packages,
though.

As I understand it, even pkg-config wants versioned
meta file names on its command line; on my
system there are 3 versions of xaw installed and
their meta files are "xaw6", "xaw7" and "xaw8";
if I try "pkg-config xaw --libs" it says to go
fly my kite.

So I have to write my own file system inspection
script to find the available versions of a package.
:-(

--
Marco Maggi

"Now feel the funk blast!"
Rage Against the Machine - "Calm like a bomb"




_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user

Re: modules and version numbers

[Ludovic Courtès]

Hi,

"Marco Maggi" <marco.maggi-ipsu@poste.it> writes:

> So I have to write my own file system inspection
> script to find the available versions of a package.
> :-(

I'd recommend against such guessing, since it can quickly become
indeterministic, unreliable, etc.

Thanks,
Ludovic.


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user