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

Barry Smith bsmith at mcs.anl.gov
Wed Jun 6 15:56:09 CDT 2012


On Jun 6, 2012, at 3:54 PM, Satish Balay wrote:

> On Wed, 6 Jun 2012, Jed Brown wrote:
> 
>> On Wed, Jun 6, 2012 at 3:40 PM, Satish Balay <balay at mcs.anl.gov> wrote:
>> 
>>> One of the concerns we discussed earlier is the additional
>>> requirement: 'subrepo' usage should be same/similar to 'single repo'
>>> usage. This clearly is not possible with (A). [we have to buy into the
>>> sub-repo model and use it appropriately].
>>> 
>>> i.e be aware which commands work with subrepos by default - and which
>>> ones need '-s' for subrepo
>>> 
>> 
>> I think most users only need to pull and update which will do the right
>> thing with subrepo.
> 
> the above requirment was discussed wrt developers [aka barry]
> 
> Also - I'm not realy sure if 'pull/update' would always do the right
> thing for users. I'll have to recheck this..

   Satish,

     You will not just "recheck this". Please setup the petsc-buildsystem-dev test repository so EVERYONE can test it and make sure there are no kinks.

   Barry

> 
> Satish
>> 
>>> - and then be aware that buildsystem you
>>> pull is not the latest [only the latest commited to petsc-dev] etc.
>>> 
>> 
>> This is the right model anyway. If a BuildSystem patch is required by
>> petsc-dev, there should be a commit in the petsc-dev repo stating that.
> 




More information about the petsc-dev mailing list