I'd like to make the final set of updates to the PETSc directory and script
naming conventions as discussed below in the next few days so please work any
branches you can through into master to reduce the extra merging you will have
to deal with later.
Jed, in particular, you've gotten so
On Tue, Jan 20, 2015 at 7:49 PM, Jed Brown wrote:
> Yeah, I would probably name it petsc-uninstall, but I'd rather have a
> single program with config and package management sub-commands. Similar to
> git or hg.
>
Yes, your petscuninstall.py should be a module imported by the main program.
Ma
Yeah, I would probably name it petsc-uninstall, but I'd rather have a single
program with config and package management sub-commands. Similar to git or hg.
On January 20, 2015 5:29:53 PM PST, Barry Smith wrote:
>
>> On Jan 20, 2015, at 6:36 PM, Jed Brown wrote:
>>
>> Barry Smith writes:
>>
>
> On Jan 20, 2015, at 6:36 PM, Jed Brown wrote:
>
> Barry Smith writes:
>
>> How about?
>>
>>share/petsc/matlab,python,julia/ non-generated stuff
>>lib/petsc/matlab,python,julia/ generated stuff for example Matlab .mex
>> files
>>
>>lib/petsc/conf
>>
>>include/petsc/f
Barry Smith writes:
> How about?
>
> share/petsc/matlab,python,julia/ non-generated stuff
> lib/petsc/matlab,python,julia/ generated stuff for example Matlab .mex
> files
>
> lib/petsc/conf
>
> include/petsc/finclude,private,mpiuni (note some generated stuff goes in
> he
Barry Smith writes:
> How about?
>
> share/petsc/matlab,python,julia/ non-generated stuff
> lib/petsc/matlab,python,julia/ generated stuff for example Matlab .mex
> files
>
> lib/petsc/conf
>
> include/petsc/finclude,private,mpiuni (note some generated stuff goes in
> he
How about?
share/petsc/matlab,python,julia/ non-generated stuff
lib/petsc/matlab,python,julia/ generated stuff for example Matlab .mex files
lib/petsc/conf
include/petsc/finclude,private,mpiuni (note some generated stuff goes in
here; could put it in lib/petsc/include b
