On Feb 15, 2010, at 3:38 AM, cschwan wrote:
Hello,
since this is my first post on this list I think it is a good idea to
briefly introduce myself: My name is Christopher Schwan, I am studying
physics at Uni Mainz (Germany) and I am one of the maintainers of
"sage-on-gentoo" (http://github.com/cschwan/sage-on-gentoo). Francois
Bissey, the other man working on it already wrote some comments about
it, but now about three months passed and I would like to report the
status of our project.
Our intention was and still is to provide so called "Split Ebuilds"
for the Gentoo Linux distribution to enable users of this distribution
to build Sage on Gentoo (since building from source is the default way
of installing programs on Gentoo). "Split" means that Sage and its
dependencies are seperately installed (and out of Sage's directories)
- we do this not only because its part of Gentoo's philosophy, but
also because of that makes it much easier maintainable.
I think we proved that this is actually possible, because we have
removed most of Sage's dependencies and only a handful are left.
Sounds like a good idea. Does the spit sage build pass all of its
tests? The one request I have is that it not go stale like the Debian
one (but it sounds like you're trying to make it maintainable).
Doing that some questions and suggestions arised which would ease
our work.
The following Tickets should be fixed imo (my top 4 bugs which should
be fixed for Sage 4.4, referring to the post of William Stein in "Vote
on bugs to be fixed for sage-4.4 "stabilization release"):
- update cvxopt, ticket #6456
- remove pyprocessing, ticket #6503
- update networkx, ticket #7608
- patch combinat, ticket #7803
Though these would be good to fix, I'm wary of all of the above for a
"stabilization release."
Questions:
- Is sqlalchemy still needed ? After removing dsage a quick grep
showed that no package in Sage uses it
I think it's used in the graph databases.
- Sage uses twisted-web2-8.1.0 which is officially deprecated.
Upgrading to twisted-web-9.x would be nice
Do you know how much work would be involved in this? IIRC,
twisted.web2 and twisted.web are very different, and it would almost
require a re-write.
- Which directories in devel/sage/build are actually needed ? They
look very similar and take quite a lot of disk space
Can't answer you on this one, this is more of a distutils question.
- Singular is heavily modified which make it impossible to split it
out of Sage - are there any intentions to send these modifications to
upstream ?
The Singular team is aware that we've made a lot of changes to their
codebase to get it into Sage, and we'd be happy to upstream. I think
it's just an issue of time on both sides.
In any case, splitting out the dependancies that are easy to split
out, and shipping a less-monolithic tarball for the rest, would still
be a good thing.
- 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
