Satish Balay <[email protected]> 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.
signature.asc
Description: PGP signature
