On 6/18/07, Brian Granger <[EMAIL PROTECTED]> wrote:
> I am talking about the both the directory structure that is needed for
> the script/makefiles to function properly:
>
> spkg/
> standard/
> base/
>
> As well as the actual scripts and makefiles (deps, install,
> newest-version, etc) th
On 6/18/07, David Harvey <[EMAIL PROTECTED]> wrote:
>
> Questions re: above package:
>
> * there are uncommitted changes in that directory i.e. "hg diff"
> gives nontrivial output. That's a bit weird. Are the changes supposed
> to be committed or rolled back?
> * there's also a lot of other cr
Questions re: above package:
* there are uncommitted changes in that directory i.e. "hg diff"
gives nontrivial output. That's a bit weird. Are the changes supposed
to be committed or rolled back?
* there's also a lot of other crud, like object files etc, probably
doesn't belong there.
On 6/18/07, Brian Granger <[EMAIL PROTECTED]> wrote:
> I didn't know SAGE was actually using them. Is this when sage -update
> is run? My understanding is that the decision to upgrade something
> was based on the timestamps if the files compared with the stub in the
> installed directory. Am I
> > Fantastic! The naming convention for spkgs that includes the .pn
> > post-fix where n labels the spkg version is probably not needed now.
> > My understanding is that label was loosely used as a sort of version
> > control. I think simply having the hg repo for each solves that
> > problem.
On 6/18/07, Brian Granger <[EMAIL PROTECTED]> wrote:
> > I've updated all spkg's so that they now have an hg repo with the
> > directory structure based on the one listed above. Comments and
> > suggestions are welcomed. You can see them here:
> > http://sage.math.washington.edu/home/dfdeshom/cust
> I've updated all spkg's so that they now have an hg repo with the
> directory structure based on the one listed above. Comments and
> suggestions are welcomed. You can see them here:
> http://sage.math.washington.edu/home/dfdeshom/custom/spkg/
Fantastic! The naming convention for spkgs that in
On 6/18/07, didier deshommes <[EMAIL PROTECTED]> wrote:
> I've updated all spkg's so that they now have an hg repo with the
> directory structure based on the one listed above. Comments and
> suggestions are welcomed. You can see them here:
> http://sage.math.washington.edu/home/dfdeshom/custom/sp
On Jun 1, 10:59 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> package_dir
> spkg-install-- (required) shell script run to install the package
> spkg-rebuild -- (optional) download latest version of package from
> web page and recreate the src directory
I can confirm that this particular test *sometimes* fails for me also.
I also don't know what the cause is.
Here is my /proc/cpuinfo.
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : AMD Athlon(tm) XP 2200+
stepping: 1
cpu MHz
I just compiled and tested sage on a machine that I haven't run it on
before, and got the following puzzling error:
sage -t devel/sage-main/sage/rings/real_mpfr.pyx
**
File "real_mpfr.pyx", line 1471:
sage: RealField(5)(-pi)
11 matches
Mail list logo
