>Part of the reason for this is that release tarballs, which contain >pre-generated configure scripts, are constructed on a machine on which the >only installed autoconf is 2.13. This could probably be changed, if the >gatekeepers decided to move forward and start requiring new autoconf, but >until it is, tossing in 2.5x dependencies will break the release process.
The problem I have is that it's not obvious to me what's an autoconf 2.5x dependency. I have the autoconf manual in front of me (it's from 2.52), and it doesn't tell me what's not in 2.13. E.g., I used AC_ARG_VAR() to declare KRB5CFLAGS and KRB5LIBS as precious, and AFAICT there's no equivalant to that in 2.13. I don't see a good way of preventing things like that unless I cross-check _every_ macro I want to use against 2.13 documentation. That kinda sucks. --Ken _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
