[petsc-dev] (no subject)

Barry Smith bsmith at mcs.anl.gov
Wed Nov 20 16:05:13 CST 2013


   Since it “is in” SuperLU  then you don’t need to make a package for it, simply require the user link in with superlu to use those functions.

   For testing you should have just put it in some branch, not in next. BTW: it generates nightly build errors that I don’t want to deal with if it is not to be kept in but they mess up next.


On Nov 20, 2013, at 3:49 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> Matthew Knepley <knepley at gmail.com> writes:
>> This http://www.hsl.rl.ac.uk/licencing.html tells me that I am not doing
>> anything wrong until we release :) 
> It says "distribute", which the public repositories and nightly tarballs
> would fall under.
>> I want this there for testing. Since it is already in SuperLU, I will
>> just move it into a package that we can download with configure. 
> Thanks, but the license would require you to download it from their site
> rather than distribute as a tarball that --download-hsl would grab.  You
> can contact them to get explicit permission.  I don't know whether
> SuperLU or Trilinos has done this, but we should not be doing it without
> permission.  If that means we cannot use HSL functions, so be it.

More information about the petsc-dev mailing list