Vanuxem Grégory wrote:
Hello,
I have uploaded a version of Axiom built on top of SBCL for Windows (32
bits).
Interesting! Not being a Windows user I can't check this out directly,
but it is good news.
I have a couple of questions concerning how this has been accomplished,
although they ma
Greg,
So far I have two problems with axiom-sbcl-win to report:
1) The )cd command does not work as expected. Here is an
example with my comments marked --->
---
C:\Documents and Settings\Administrator.ASUS\Desktop>set
AXIOM=C:\cygwin\home\Administrator\axiom-sbcl-win
C:\Documents and S
Greg,
On February 11, 2007 4:53 PM you wrote:
> ...
> I wrote:
> > I get the following result on by Windows XP SP2 system while
> > running under Cygwin, using 'wget ...' and 'tar xjvf' to
> > extract the binary and setting the AXIOM variable:
> >
> > $ echo $AXIOM
> > /home/Administrator/axiom-sb
> -Message d'origine-
> De : Bill Page [mailto:[EMAIL PROTECTED]
> Envoyé : dimanche 11 février 2007 22:25
> À : 'Vanuxem Grégory'
> Cc : 'Axiom-Developer'
> Objet : RE: [Axiom-developer] Request for testing (Win32 users)
>
>
> Greg,
>
> You wrote:
>
> > ...
> > To use it, untar/unbzip2 it
Greg,
You wrote:
> ...
> To use it, untar/unbzip2 it in a directory without space in its
> name (full path without space).
> Export the environment variable AXIOM, it must point to the
> directory that contains the algebra, bin etc... directories.
>
> So for example:
>
> set AXIOM=c:\somewhere\ax
On February 11, 2007 1:22 PM Vanuxem Grégory wrote:
>
> I have uploaded a version of Axiom built on top of SBCL for
> Windows (32 bits). So if you are a Windows user, you already
> know Axiom and you can spent some time for testing and reporting
> bugs I would really be happy.
Great! I am very g
On Sun, 11 Feb 2007, Alfredo Portes wrote:
| Hi Gaby,
|
| > I propose the numbering X.Y.Z, with
| >
| > * X == major release number
| > * Y == minor release number
| > * Z == patch level release number
| >
| > I propose that the next version be 3.5.0, with subsequent bug fix
| > releases, be
[EMAIL PROTECTED] writes:
1) IMHO publish release as CVS tree on SorceForge is bad practice...
That's unlikely to change, at least by me. I'm only trying to maintain
the source tree, not the release of binaries.
I mean only source release tarball not any binaries.
--
Vadim V. Zhytniko
Hi Gaby,
I propose the numbering X.Y.Z, with
* X == major release number
* Y == minor release number
* Z == patch level release number
I propose that the next version be 3.5.0, with subsequent bug fix
releases, be 3.5.x.
When we merge build-improvements to trunk, I would suggest we bump
[EMAIL PROTECTED] writes:
[...]
| > 2) I'd like to see some consistent version numbering scheme
|
| Check the mailing list archives. We've had this discussion and
| several schemes were proposed, such as the usual Major.Minor.Patch
| schemes. We settled on a version scheme, which is consiste
"Do not discuss issues related to this version on the official Axiom
mailing lists unless explicitly permitted"
Well, it's axiom. it's in development. this is the most likely place
to discuss it. you don't need permission to discuss anything on this
list (although some topics, like legal topics w
Hello,
I have uploaded a version of Axiom built on top of SBCL for Windows (32
bits).
So if you are a Windows user, you already know Axiom and you can spent some
time
for testing and reporting bugs I would really be happy.
Things that you have to know:
* You must know Axiom,
* You have an offici
> 1) IMHO publish release as CVS tree on SorceForge is bad practice...
That's unlikely to change, at least by me. I'm only trying to maintain
the source tree, not the release of binaries. The sources also live at
savannah.nongnu.org (CVS), axiom-developer.org (arch), and
sourceforge.net (SVN), as
"Vadim V. Zhytnikov" <[EMAIL PROTECTED]> writes:
[...]
| 1) IMHO publish release as CVS tree on SorceForge
| is bad practice. To make sure whether something
| have changed or I still have some old release
| I have to check all hundreds of files in CVS tree.
| Publishing release as a single file
root <[EMAIL PROTECTED]> writes:
So I'm resuming my role as "Lead Developer" and will generate a new release
in the near future.
This is really good news!
But maybe you find it possible to change the way
how Axiom releases are actually released.
1) IMHO publish release as CVS tree on Sorce
15 matches
Mail list logo
