Dear all, especially Alfredo and Bill!
First of all, I would like to say a big THANK YOU! for your encouragement and
your energy, although it has not quite worked out.
However: If you would save the image somewhere so I can download it, I could
burn a couple of CD's tonight.
I must confirm that
On 19 Sep 2006 23:10:44 +0200, Gabriel Dos Reis
<[EMAIL PROTECTED]> wrote:
"Alfredo Portes" <[EMAIL PROTECTED]> writes:
| Apparently Google did not increase the size to 200 MB.
I got an email that the hosting team would get into contact with me.
I'll ping them.
-- Gaby
Thanks Gaby.
___
"Alfredo Portes" <[EMAIL PROTECTED]> writes:
| Apparently Google did not increase the size to 200 MB.
I got an email that the hosting team would get into contact with me.
I'll ping them.
-- Gaby
___
Axiom-developer mailing list
Axiom-developer@nongnu
The terminology is still rather confusing, but from my point
of view the axiom.build-improvements branch is a branch of
Silver. So I guess you are asking whether you should put the
Silver *trunk* branch into the Google Code archive?
Sorry, I should be more explicit :) . Yes I meant having the Si
On Tuesday, September 19, 2006 1:18 PM Alfredo Portes wrote:
>
>
> For what I have read, build-improvements will be gone after
> Gaby's work is completed and added to Silver -> Gold.
>
It wont be gone, it will be merged back into Silver Trunk and
someday merged into Gold (if/when Tim Daly is co
In spite of planning the mirror the SourceForge SVN archive on
axiom-developer.org, I think maintaining a smaller archive on Google -
containing only the most experimental branch, i.e. build-improvements,
is still a good idea.
Of course this needs someone to manage it and keep it up to date
with
Sorry for disappearing suddenly, my internet connection went down. I'm
not sure what the problem was but it works again.
root <[EMAIL PROTECTED]> writes:
> 2) Tim looked at porting Axiom to the MAC.
>
>There is an outstanding GCL issue. GCL save-system cannot save
>images that will execu
So, just to confirm: if you follow all 10 of Martin's steps starting
with patch-49 do you obtain a working version of Axiom including
Hyperdoc and graphics?
Yes. I just finished a new trial again with 49 and 50 at the same time.
50 breaks, 49 doesn't. I hope somebody can reproduce this.
__
Alfredo,
On September 18, 2006 6:52 PM you wrote:
>
> Well, I just finished building using patch-49 as Bill suggested me.
> Hyperdoc worked fine after doing just one step, which using patch-50
> it was breaking for me (I am really sorry Martin :-( ). I would like
> to know if Martin was using pat
3) Tim spent time this weekend looking into Martin's build issues
without success.
Suggestion that Jose send a diff of his changes to --patch-50
so Tim can see what approach he was taking
Well, I just finished building using patch-49 as Bill suggested me.
Hyperdoc worked fine after do
Alfredo,
On September 18, 2006 4:15 PM you wrote:
> Tim Daly wrote:
> > 9) Google objects to having binaries in the zips directory.
> >It was agreed that since Google was only a method of getting
> >around the breakage of Sourcforge SVN and that we plan to put
> >SVN on axiom-develope
Tim --
Many thanks for posting the summary of the conference.
Below I add a small precision.
root <[EMAIL PROTECTED]> writes:
[...]
| 5) Indefinites.
|
|Tim mentioned that indefinites could be done using provisos.
|
|Bill objected that provisos was a proof-theoretic approach
|a
9) Google objects to having binaries in the zips directory.
It was agreed that since Google was only a method of getting
around the breakage of Sourcforge SVN and that we plan to put
SVN on axiom-developer therefore we should ignore Google going
forward.
Should the project be deleted
Participants: Kai Kaminski, Gabriel Dos Reis, Bill Page, Tim Daly
Start: 1pm
End: 2pm
1) Bill looked into the details of SVN/SVK on axiom-developer.org
but has not yet succeeded in building an installation.
2) Tim looked at porting Axiom to the MAC.
There is an outstanding GCL issue. GCL
14 matches
Mail list logo
