[petsc-dev] Notification: Fwd: You have hereby been granted admin access to jedbrown/petsc-dev.

[Barry Smith]

  In petsc-XXX/config/   what will you call BuildSystem?  BuildSystem, buildsystem, buildsystem-dev, buildsystem-XXX

   It would be nice to have totally consistent naming of the same thing in different places but do we really want petsc-XXX/config/buildsystem-yyy where
yyy is different depending on release or dev? 


    Barry


On Nov 16, 2012, at 10:28 AM, Satish Balay <balay at mcs.anl.gov> wrote:

> On Sun, 11 Nov 2012, Jed Brown wrote:
> 
>> On Sun, Nov 11, 2012 at 11:38 PM, Satish Balay <balay at mcs.anl.gov> wrote:
>> 
>>> Just want to mention 2 -ves for this namechange.
>>> 
>>> 1. config/PETSc, config/BuildSystem were supporsed to be 2 components
>>> here [now the naming between them will be inconsistant. Not a big
>>> deal]
>>> 
>>> 3. all petsc dev users would have to rename their current buildsytem -
>>> if not configure will autoclone a second one. This can cause some
>>> grief. Perhaps this can be handled by some detection code - and giving
>>> a warnig/error [or rig configure to use BuildSystem or buildsystem]
>>> 
>> 
>> We could put some rename/reset code in there.
> 
> I'm inclined towards renaming buildsystem to buildsystem-dev [to be
> conisitant with petsc-dev]. We will similarly have petsc-release and
> buildsystem-release
> 
> The user [or configure auto-clone code] would do the following
> 
> hg clone https://bitbucket.org/petsc/petsc-dev
> hg clone https://bitbucket.org/petsc/buildsystem-dev petsc-dev/config/BuildSystem
> 
> or
> 
> hg clone https://bitbucket.org/petsc/petsc-release
> hg clone https://bitbucket.org/petsc/buildsystem-release petsc-dev/config/BuildSystem
> 
> [and not change PETSc code to use 'buildsystem' - and have users
> change their BuildSystem repos. Only change would be in
> BuildSystem/.hg/hgrc]
> 
> Satish