2009/11/18 Georg S. Weber <georgswe...@googlemail.com>:
> Hi,
>
> this is circle of questions coming up every now and then, I try to
> give a complete yet not too long answer.
>
> The Sage community is limited in resources, and for the time being,
> the focus is set e.g. to further broaden the number of systems that
> are supported. Solaris and BSD are on a good way, but not completely
> done yet AFAIK, considerable efforts are spent on Cygwin, and native
> support for Windows (both in 32bit and 64bit mode) is envisaged.
>
> Given this and other arguments, a clear and precise design decision
> has been made --- there is one and only one Sage distribution which
> includes "almost everything", but which (builds and) runs on a large
> variety of systems at one and the same time, with as few system-
> dependent deviations as possible (for easy maintainability).
>
> This design decision allows for some comfort, e.g. you can move around
> the whole Sage tree, and upon startup, some internal hardcoded paths
> have to be adjusted once, but then it runs fine. Or else, you could
> install Sage-2.9 (say) and Sage-4.2 at the same time (in different
> directories of course), although these two version of Sage might
> depend on different (even incompatible) libraries/progams resp.
> versions of libraries/programs (to be found under the respective
> SAGE_ROOT/local/lib/ and SAGE_ROOT/local/bin/ directories). Another
> benefit is the possibility to distribute precompiled binary
> distributions of Sage (that can be more or less just copied to some
> directory of the users choice).
>
> That said, there should be no need to "rip out some libraries", and
> there should not be collisions. Everything is supposed to live happily
> side-by-side. If problems happen (and they do), usually some
> environment settings are messed up --- or it is a bug in Sage.
>
> Of course there dreams of providing version of Sage that are simply
> "apt-gettable" into current Debian/Ubuntu installs, to have Sage-
> x.y.z.rpm's for Fedora, and so on (I remember some recent work for
> Mandriva in that direction). But currently, simply the manpower lacks
> to do the necessary building and testing (resp. the possibly available
> forces are occupied with tasks that at the moment are considered to be
> more important).
Mandriva release 2010.0 recently, and now I am working on newer
sagemath packages for cooker.
I understand that packaging sage spkgs in some distros may have
too much obstacles, because most patches are sage specific or not
forwarded/merged upstream. Or just because sage uses an older version,
again, the problem of lack of manpower.
From my experience (now running "native" Mandriva cooker sage 4.2),
the major problem is doctest failures, mostly not really a problem,
for example:
File "/usr/share/sage/devel/doc/common/builder.py", line 158:
sage: b._output_dir('html')
Expected:
'.../devel/sage/doc/output/html/en/tutorial'
Got:
'/usr/share/sage/devel/doc/output/html/en/tutorial'
...
File "/usr/share/sage/devel/doc/en/constructions/graph_theory.rst", line 19:
sage: C = graphs.CubeGraph(4)
Expected nothing
Got:
doctest:16: DeprecationWarning: the sets module is deprecated
...
File "/usr/share/sage/devel/doc/en/constructions/polynomials.rst", line 45:
sage: print gap.eval("R:= PolynomialRing( GF(97))")
Expected:
PolynomialRing(..., [ x_1 ])
Got:
GF(97)[x_1]
...
and so on.
The major benefit is probably load time as there is no change to
LD_LIBRARY_PATH, etc. Example:
% echo quit | sage
----------------------------------------------------------------------
| Sage Version 4.2, Release Date: 2009-10-24 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------
sage: Exiting SAGE (CPU time 0m0.03s, Wall time 0m0.03s).
and binary (for Mandriva 2009.1) sage:
% cd ~/sage-4.2
% echo quit | ./sage
----------------------------------------------------------------------
| Sage Version 4.2, Release Date: 2009-10-24 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------
sage: Exiting SAGE (CPU time 0m0.10s, Wall time 0m0.11s).
> Help is always welcome, and be it in the form of a precise bug report
> --- what kind of problem do you have with gnutls?
>
> Cheers,
> Georg
>
> P.S.:
> William et.al., please feel free to correct me ...
Paulo
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
