changes to petsc-dev directories

[Barry Smith]

    Very valid point.

    Barry

On Dec 14, 2007, at 7:37 PM, Dmitry Karpeev wrote:

> If maint/ is going into bin/maint/, I think config/ should also go  
> to bin/config/
> (I think someone already suggested it).  The reason is that these  
> are auxiliary scripts
> used to configure and build PETSc.  Their output -- the actual PETSc  
> configuration --
> goes into conf/ and ${PETSC_ARCH}/conf and everything makes sense.
>
> Besides, there is no need to install bin/config/ and violate one  
> standard or another,
> since an installation implies a particular configuration, which is  
> already in
> conf/ etc.
>
> Dmitry.
>
> On 12/14/07, Satish Balay <balay at mcs.anl.gov> wrote:
> Reforwarding e-mail blocked by majordomo [reason: ^config is special
> command to majordomo]
>
> Satish
>
> ---------- Forwarded message ----------
> From: Barry Smith <bsmith at mcs.anl.gov >
> To: petsc-dev at mcs.anl.gov
> Subject: changes to petsc-dev directories
> Date: Sat, 8 Dec 2007 21:55:10 -0600
>
>      I have moved python/PETSc to config/PETSc and python/ 
> BuildSystem to
>   config/BuildSystem
>   in addition I have moved the maint directory to bin/maint and  
> removed
>   conf/rules.basic.shared
>
>   After your next hg pull do:
>   mv python/BuildSystem config
>   rm -rf python
>
>     Any user makefiles and code should not need any changes
>
>       Barry
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20071214/daad2d07/attachment.html>