<html><head></head><body>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.<br><br><div class="gmail_quote">On January 20, 2015 5:29:53 PM PST, Barry Smith <bsmith@mcs.anl.gov> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> On Jan 20, 2015, at 6:36 PM, Jed Brown <jed@jedbrown.org> wrote:<br /> <br /> Barry Smith <bsmith@mcs.anl.gov> writes:<br /> <br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> How about?<br /> <br /> share/petsc/matlab,python,julia/ non-generated stuff <br /> lib/petsc/matlab,python,julia/ generated stuff for example Matlab .mex files<br /> <br /> lib/petsc/conf <br /> <br /> 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)<br /></blockquote> <br /> The above is good.<br /> <br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> bin/petsc/mpiexec.uni when using uni<br />
bin/petsc/<a href="http://uninstall.py">uninstall.py</a><br /></blockquote> <br /> $ find /bin/ -type d<br /> /bin/<br /> /bin/core_perl<br /> /bin/vendor_perl<br /> /bin/cgnstools<br /> /bin/site_perl<br /> $ find /bin/ -type f | wc<br /> 4181 4181 65101<br /> $<br /> <br /> I'd rather not add a directory in bin.<br /> <br /> I think uninstall should go in sbin.<br /></blockquote><br /> Called what? <a href="http://petscuninstall.py">petscuninstall.py</a> ? Is it ok to put a python script there?<br /><br /><br /><br /></pre></blockquote></div></body></html>