On Dec 27, 5:27 pm, Pablo De Napoli wrote:
> > SAGE_CHECK=yes does that for every spkg, adding 50+ env variables for
> > all the spkgs seems like a bad idea and won't automatically force the
> > test suite when we want it to be tested.
>
> I agree. 50+ env-variables is not a good idea.
> SAGE_C
>
> SAGE_CHECK=yes does that for every spkg, adding 50+ env variables for
> all the spkgs seems like a bad idea and won't automatically force the
> test suite when we want it to be tested.
I agree. 50+ env-variables is not a good idea.
SAGE_CHECK is ok
Cheers,
Pablo
--~--~-~--~~
On Dec 27, 3:38 am, Sun wrote:
Hi,
> On Dec 27, 4:42 am, Harald Schilly wrote:
>
> > On Dec 26, 6:25 pm, mabshoff wrote:
>
> > > By the way: On December 23rd we got a log of traffic from this Chinese
> > > blog:http://linux.chinaunix.net/news/2008/12/23/1054171.shtml
>
> Well it's something
On Dec 27, 8:31 am, Pablo De Napoli wrote:
Hi Pablo,
> I see that the file skpg-install for flint needs to be modified in final
> releases to avoid runing the test suite.
There was already a ticket to do that before 3.2.3.a0 was even
released :)
> I think it would be better to have for exam
I see that the file skpg-install for flint needs to be modified in final
releases to avoid runing the test suite.
I think it would be better to have for example an environment variable like
SAGE_RUN_FLINT_TESTSUITE (and run the test suite or not depending on the value
of that variable) that w
On Dec 27, 4:42 am, Harald Schilly wrote:
> On Dec 26, 6:25 pm, mabshoff wrote:
>
> > By the way: On December 23rd we got a log of traffic from this Chinese
> > blog:http://linux.chinaunix.net/news/2008/12/23/1054171.shtml
Well it's something introductory about Sage, obviously positive and
with
