[petsc-dev] Always compiling and installing Ctetgen even without updates

[Barry Smith]

> On Jan 28, 2016, at 12:42 AM, Jed Brown <jed at jedbrown.org> wrote:
> 
> Satish Balay <balay at mcs.anl.gov> writes:
>> But tetgen depends on petsc includes - so a pull could change any of
>> these files [so somehow all include deps should be tracked?]
> 
> Naturally.  I would do this by adding an include (listing ctetgen
> sources and target lib) to gmakefile (supporting the same for other
> build systems is more of a hassle).
> 
> However, I think this is a crappy way to distribute software and Matt
> should have kept ctetgen a stand-alone package instead of inlining it
> into PETSc source tree (which broke the license terms) and then having
> it be only partially divorced.

  Yeah, I tried to disentangle it but PETSc was so embedded in it I gave up.