[petsc-dev] Fwd: [petsc-maint #119133] petsc-dev configure crash

Barry Smith bsmith at mcs.anl.gov
Wed Jun 6 15:03:05 CDT 2012

On Jun 6, 2012, at 2:57 PM, Sean Farley wrote:

>>> A) make buildsystem a subrepo (svn external for those familiar with svn)
>>   There have already been many discussions on petsc-dev about how hg subrepos suck and don't satisfy all our needs.
> That's why I asked about a current list to see exactly what need isn't
> met.

     Check the old email. Satish and Matt had specific concerns.

> So far, I only have that older mercurial clients wouldn't be able
> to push (but pulling should work fine); so all devs would need a
> recent mercurial client.

   As I mentioned in my email to Jed. There needs to be a way to enforce the use of a recent mercurial client.

>>> B) merge buildsystem into petsc-dev and use graft / transplant to
>>> maintain a separate repo
>>   Yuck.
> Yuck? Everyone would win: Matt would have his separate repo and there
> would be no more unsynchronized changesets.

    It sounds hacky. If it is not hacky and Matt is fine with this then we could go that route.


More information about the petsc-dev mailing list