Lisandro, I think this is going to depend on what your release cycle looks like over the next year in comparison with the PETSc team. If the two teams can coordinate releases, I think it is better to be working against PETSc releases.
A On Thu, Sep 16, 2010 at 6:18 PM, Lisandro Dalcin <dalcinl at gmail.com> wrote: > I've managed to backport setup.py to release-3.1. It does not require > any change to BuildSystem or install.py, as I'm simply using > os.system() to spawn configure, make and install. Matt agreed that we > could add setup.py to release-3.1 (as it would not break anything), > and then get the beast working right now. As a plus, this could also > be done with SLEPc and slepc4py. > > Other far less intrusive alternative would be to just upload PETSc > (and SLEPc) tarballs to PyPI containing my setup.py. Then nothing have > to be done with current PETSc and SLEPc releases. What do you think? > > -- > Lisandro Dalcin > --------------- > CIMEC (INTEC/CONICET-UNL) > Predio CONICET-Santa Fe > Colectora RN 168 Km 472, Paraje El Pozo > Tel: +54-342-4511594 (ext 1011) > Tel/Fax: +54-342-4511169 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100916/5069b17f/attachment.html>
