David Brownlee <abs%absd.org@localhost> writes: >> ** GCC_REQD >> >> the minimum gcc version needed, with the semantics that all higher >> versions are ok. Does not imply anything at all about clang. >> >> ** GCC_INCOMPATIBLE >> >> gcc versions > $GCC_REQD that are known not to work for this package > > Maybe make it more explicit with something like GCC_MIN_VERSION & > GCC_MAX_VERSION? On GCC_MIN_VERSION, I agree. Then I'd want GCC_INCOMPATIBLE_VERSIONS to be a list. The point is that I don't think we can predict what will and won't work for any particular package, since in an ideal world we wouldn't have this problem at all. > We seem to have a pattern of PREFER rather than DESIRE in making (I > make no comment regarding the complete lack of "DESIRE in pkgsrc/mk :) > I would have this value purely be of the form 41 or 49 without > reference to base: or pkgsrc: Sure, that sounds fine. To me, the important thing is that each variable should either be settable by a package or in mk.conf, not used in both environments. > Other than a mild view regarding the colour of the variable names, > what you have written matches what I would have put had I thought it > through and been able to articulate it clearly :) Thanks - I didn't feel super coherent writing this....
Attachment:
pgpaiNNw1TPM6.pgp
Description: PGP signature