> > I agree that petsc/include/petsc is stupid. I see no reason to change the > perfectly logical include/private just to match what > some idiot programmers did. >
Huh? So, if I install petsc with a --prefix, and (god-forbid!) some other project also has a 'private' directory, then there's now a conflict. Jed isn't just pulling this convention out of his ass here. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120312/136a6885/attachment.html>
