Lisandro, I don't understand this. Are you saying that the PETSc installer installs a bunch of files it shouldn't so you strip them out after the install is run?
The PETSc installer is a nice flexible piece of python code. I don't understand why you people who understand which files shouldn't be installed don't just edit the installer to prevent it from installing things it shouldn't instead of writing ad hoc post-install cleanup scripts. Why is "fixing" the installer so difficult that you guys just leave it in a broken state for years? (The reason I don't "fix" it is that I don't know what needs to be fixed since I don't interact with the package managers. Barry > On Feb 25, 2018, at 1:43 AM, Lisandro Dalcin <dalc...@gmail.com> wrote: > > > > On 23 February 2018 at 23:31, Matthew Knepley <knep...@gmail.com> wrote: > On Fri, Feb 23, 2018 at 3:19 PM, Jed Brown <j...@jedbrown.org> wrote: > What, if anything, really needs to be installed to $prefix/bin? > > From the Homebrew lead maintainer. > > The maintainer of Homebrew calling anything a mess is pretty rich. > > > Look at my approach to fix the mess: > > https://github.com/conda-forge/petsc-feedstock/blob/master/recipe/build.sh#L53 > > > Matt > > > ---------- Forwarded message ---------- > From: Mike McQuaid <notificati...@github.com> > To: "Homebrew/homebrew-core" <homebrew-c...@noreply.github.com> > Cc: Jed Brown <j...@jedbrown.org>, Mention <ment...@noreply.github.com> > Bcc: > Date: Fri, 23 Feb 2018 19:59:53 +0000 (UTC) > Subject: Re: [Homebrew/homebrew-core] PETSc: import from homebrew-science > (#23598) > doesn't this attitude complete defeat the purpose of a package manager? > > You're asking of the hardest working package manager maintainers in the world > (@ilovezfs). Chances he has a better idea about the purpose of a package > manager than you do. > > I cannot understand not wanting a package because it is complicated to > install. > > This is perhaps because you do not maintain a package manager. > > What you're suggesting is that any software using PETSc should either force > users to compile it from scratch or discontinue supporting macOS entirely. > > No, what's being suggested is that PETSc's currently upstream installation is > a mess and we don't want to maintain the hacks required to make it not one > indefinitely. You can copy and paste this formula as-is into a tap and it'll > work for you just fine. > > That seems like the wrong approach for a package manager. > > In the package manager you maintain you should take a different approach, > then. > > Just my opinion... > > If you have to end your statement like that: it's probably worth keeping > quiet in future, please. > > To be clear, I'm not being harsh here because I like doing so but because > this entitled, know-it-all attitude literally kills open source projects and > @ilovezfs's motivation is more important to me than allowing that to go > unchallenged. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread. > > > > > > -- > What most experimenters take for granted before they begin their experiments > is infinitely more interesting than any results to which their experiments > lead. > -- Norbert Wiener > > https://www.cse.buffalo.edu/~knepley/ > > > > -- > Lisandro Dalcin > ============ > Research Scientist > Computer, Electrical and Mathematical Sciences & Engineering (CEMSE) > Extreme Computing Research Center (ECRC) > King Abdullah University of Science and Technology (KAUST) > http://ecrc.kaust.edu.sa/ > > 4700 King Abdullah University of Science and Technology > al-Khawarizmi Bldg (Bldg 1), Office # 0109 > Thuwal 23955-6900, Kingdom of Saudi Arabia > http://www.kaust.edu.sa > > Office Phone: +966 12 808-0459