[petsc-dev] prefix installs and lib/petsc-conf

[Jed Brown]

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 <bsmith at mcs.anl.gov> wrote:
>
>> On Jan 20, 2015, at 6:36 PM, Jed Brown <jed at jedbrown.org> wrote:
>> 
>> Barry Smith <bsmith at mcs.anl.gov> 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 here; could put it in lib/petsc/include but that seems silly to
>me)
>> 
>> The above is good.
>> 
>>>    bin/petsc/mpiexec.uni  when using uni
>>>    bin/petsc/uninstall.py
>> 
>> $ find /bin/ -type d
>> /bin/
>> /bin/core_perl
>> /bin/vendor_perl
>> /bin/cgnstools
>> /bin/site_perl
>> $ find /bin/ -type f | wc
>>   4181    4181   65101
>> $
>> 
>> I'd rather not add a directory in bin.
>> 
>> I think uninstall should go in sbin.
>
>Called what? petscuninstall.py ? Is it ok to put a python script there?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150120/23a696ff/attachment.html>