Hi,
"Marco Maggi" <[EMAIL PROTECTED]> 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.
"Andy Wingo" wrote:
>On Fri 05 Oct 2007 16:34, "Marco Maggi"
<[EMAIL PROTECTED]> 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, sp
Hi,
On Fri 05 Oct 2007 16:34, "Marco Maggi" <[EMAIL PROTECTED]> 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 o
Hi Marco,
"Marco Maggi" <[EMAIL PROTECTED]> 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))'.
L
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 l
