Lisandro,
You never responded to this. I assume it was because you did not like the
idea? This is not an attempt to take control of petsc4py or to take credit away
from petsc4py from you. Petsc4py is your package and you will always be the one
who deserves the credit.
The problem is that mutual efficient development of very intertwined
packages is difficult if they are in different respositories. For example
petsc4py has been out of date with petsc master for many weeks now because it
is too much effort to update the petsc4py repository each time we make some
change in PETSc. Thus it becomes a burden on you to go in every once in a while
and fix up petsc4py. With one repository changes would happen in both PETSc
source and petsc4py source at the same time and tests would detect problems
immediately.
Thoughts?
Barry
> On Sep 22, 2015, at 3:39 PM, Barry Smith <[email protected]> wrote:
>
>
> Lisandro,
>
> Now that everyone is using git and knows branches well can we move
> PETSc4py inside the PETSc repository as was done a couple of years ago with
> BuildSystem. Now when changes/additions are made to PETSc there is a slow
> inefficient, often forgotten manual process of bringing them over to
> petsc4py. If we put them all in one repository the updates happen quickly and
> far more efficiently, as would testing. We'll also get the ability to do
> bi-section.
>
> I realize you want a PETSc4py release to be compatible with previous
> versions of PETSc; this property could still remain and we could easily have
> a tool that "pulls out" the petsc4py release material from the petsc
> repository.
>
> I think once we make this change we'll wonder why we didn't do it log ago;
> just as when we changed BuildSystem. Thoughts?
>
> Thanks
>
> Barry
>
