On Mar 17, 2010, at 8:11 PM, Dr. David Kirkby wrote:
Robert Bradshaw wrote:
On Mar 17, 2010, at 4:52 PM, Dr. David Kirkby wrote:
William Stein wrote:
On Wed, Mar 17, 2010 at 4:20 PM, Dr. David Kirkby
<david.kir...@onetel.net> wrote:
I started a build of Sage 4.3.4.rc0 on 't2' and one of my own
SPARCs. The
build on 't2' is still going but it completed on on of my SPARCs
at home. I
just started to run the long doctests.
Yeah! All this successful work on Sage+Solaris is great.
Yes.
To
celebrate, I've created a new mailing list:
http://groups.google.com/group/sage-solaris
which is for all discussions related to Solaris and Sage. I would
like to encourage *everybody* reading this with an interest in
Solaris
to subscribe, and also like to strongly encourage new threads
that are
only relevant to Solaris/Sage to get posted there (rather than
sage-devel).
-- William
Personally I think that was a *very* bad idea. 95% of people won't
read the list, so 95% of people will not read particular problems
that were created by others that have an impact on Solaris.
Are there lists for Debian, Ubuntu, CentOS, Fedora, SUSE, Mandriva
or OS X?
These systems don't cause near the traffic. We have a separate list
for the Windows/cygwin efforts. Most people on sage-devel don't
touch anything that will impact Solaris (e.g. they only mess with
Python code in the Sage library itself), and release managers, etc.
will be on that list.
Now Sage is building on Solaris 10 (SPARC), the volume of traffic
about Solaris 10 (on SPARC) should drop. If changes are made that do
not affect Solaris 10 on SPARC, then then there will be no posts
about Solaris 10 on SPARC.
If you look at the number of posts by me since 4.3.4.alpha1 was
released and working, there are very few. Some reported things like
I guess I've kind of felt inundated by Solaris posts lately. I am very
glad the Solaris port is going so well, but the number of messages
were starting to number 100s a month, and the vast majority of them
were completely irrelevant to me. I've talked to other people who feel
the same way. Most people who develop Sage do not code shell scripts,
edit makefiles, or twiddle with command line flags--let alone try to
do so on Solaris.
If the level of traffic drops off to what it is for other systems (and
you're right, it has lately), then segregating it out won't be as
important. If a host of new issues arise when porting Sage to
OpenSolaris and Solaris x86 then I don't think all of sage-devel needs
to know about them.
This will simply isolate Solaris and make it more difficult to
keep Sage building on Solaris.
That is true to some extent.
I think the word "some" understates this considerably. If updates
are made to packages which break on Solaris, but are only reported
on a Solaris-specific list, then the Sage will soon stop working on
Solaris.
Hopefully there will be a policy that Sage builds and passes all tests
on Solaris before every release. Doctest and build failures should
alway get to sage-release.
- Robert
--
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
