Differences between revisions 16 and 18 (spanning 2 versions)
⇤ ← Revision 16 as of 2008-02-08 09:48:43 →
Size: 1792
Editor: OndrejCertik
Comment:
← Revision 18 as of 2008-02-08 22:14:11 → ⇥
Size: 1755
Editor: MichaelAbshoff
Comment: Update Plan to Plan/Status
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * Infrastructure, setup and progress at [:days7/DebianPackagingSprint:Debian Packing Sprint during Sage Days 7]
Line 28: Line 29:
== Work ==

There is a lot of stuff happening at SD7:

[:days7/DebianPackagingSprint:]

== Plan ==		 == Plan/Status ==
Line 38: Line 33:
  * wait a year or so, until SAGE settles some more
  * fix patches in spkg, so that it works both for SAGE and outside of SAGE; get those patches to Debian
  * package those packages that will not work outside SAGE in /usr/share/SAGE, or something.
  * try to package the packages in Debian independently so that we have a good knowledge of any policy issue with files shipped in the packages
    * that are non-free but not used in SAGE
    * that are automatically generated but which cannot be built easily 		  * redesign spkg-install to handle distribution packages (done for Debian, patch will be in 2.10.2)
  * create Debian packages for spkgs not in Debian (nearly done, sage-*.spkg still missing)
  * use existing packages from testing and track down the debs in testing that cause doctest failures. Resolve those issues
  * Expand the building to non-testing and track down failures in existing debs. Investigate the use of backports.org for those debs

Debian SAGE Packaging Team (DSPT)

Task description

Currently [http://sagemath.org/ SAGE] is not in Debian yet. This team wants to make this happen.

Infrastructure

People

(Please add yourself below, if you want to help)

Other

We are aware of the official Debian Alioth project and mailing lists and later we can move things to Alioth if we decide to do so. But the google groups interface is nice and also the "debian-sage" project is not official in Debian (yet), but we already need to coordinate efforts.

Plan/Status

The following items should be done in parallel:

  • redesign spkg-install to handle distribution packages (done for Debian, patch will be in 2.10.2)
  • create Debian packages for spkgs not in Debian (nearly done, sage-*.spkg still missing)
  • use existing packages from testing and track down the debs in testing that cause doctest failures. Resolve those issues
  • Expand the building to non-testing and track down failures in existing debs. Investigate the use of backports.org for those debs

See the team mailinglist for uptodate information on what is happening.