[petsc-dev] petsc release soon

[Barry Smith]

On Mar 12, 2012, at 1:51 PM, Satish Balay wrote:

> On Mon, 12 Mar 2012, Barry Smith wrote:
> 
>> 
>> On Mar 12, 2012, at 1:36 PM, Jed Brown wrote:
>>> 
>>> 3. Move all private headers from include/private/ to include/petsc/ (convention adopted by hundreds of packages) or include/petsc-private/ (like Tk).
>> 
>>  I prefer petsc-private because if one installs in the xxxx/petsc/  you get this stupid looking  xxxx/petsc/include/petsc.   Better xxxx/petsc/include/petsc-private
> 
> Personally - I'm fine with include/petsc/. But isn't this notation
> more for having 'all' includes in '/usr/include/petsc' - and not for
> spliting them in 2 dirs /usr/include/, /usr/include/petsc

    This is why include/petsc  directory doesn't work. People will be confused between the include/petscvec.h and the include/petsc/vecimpl.h   by naming it explicitly include/petsc-private/vecimpl.h it is clearly part of petsc but also clearly labeled as private so not to be confused with the high level include/petscvec.h files.

   Barry

> 
> Also - I see the following notation used for mutiple version installs..
> 
> balay at petsc:/usr/include $ ls -ld py*
> drwxr-xr-x 3 root root 4096 2010-07-26 17:05 python2.5/
> drwxr-xr-x 5 root root 4096 2010-10-06 07:41 python2.6/
> drwxr-xr-x 2 root root 4096 2011-09-09 07:47 python2.6_d/
> drwxr-xr-x 2 root root 4096 2011-12-20 08:05 python3.1/
> 
> 
> Satish