Summary: | sci-libs/plplot: patch (plplot-5.5.1-gcc-3.4-fix.patch) changes both autotools source and result | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 226305 |
Description
Diego Elio Pettenò (RETIRED)
![]() Hi Diego, I presume it would also be ok to patch Makefile.in *only* which would be sufficient to get plplot to compile against octave? Thanks, Markus Uh no, patching Makefile.am and .in is opinable (I find it not entirely safe as it might cause maintainer mode to trigger), patching just Makefile.in is simply wrong because the first time someone else add another patch that requires rebuilding autotools, your Makefile.in patch is gone. Hi Diego! Thanks for the note and that makes sense. However, this then also implies to me that any patching of *.in files or configure itself for that matter carries that same danger, which in turn implies that any patching that affects some autotool component should always be done to configure.ac and Makefile.am only. Is there something I am missing here or is that indeed the proper policy for dealing with autotools? I am curious, because I've seen (and personally added) quite a few patches to configure itself for example. Thanks much for explanations; I appreciate them! Best, Markus Will probably not get fixed now plplot is at much later version and with cmake. Keeping it open until we have newer version stabilized. plplot-5.5.x gone. |