Simon Josefsson wrote: > On CI using latest gnulib > for each OS, you would want to build with both > latest and the GNULIB_REVISION pinned gnulib. That is a lot of > energy/CPU usage.
The inetutils builds take 12 minutes; I have little remorse regarding these builds (that happen once a week), compared to the gettext or libtool builds that take 2-3 hours. > - My primary use of CI is to have confidence in the tarball I release, > thus it is important to widely test the actual gnulib commit used for > the release on many platforms. That is, well, an "occasional" build, not a "continuous" build. One of my packages (libffcall) uses an occasional build, and just yesterday I had to fix a regression that I made 11 months ago. It costs me more time to fix a bug after 11 months than after at most one week: the time to re-think about the old patches that are not present in memory any more. The advantage of a "continuous" build is also that any new maintainer can make a new release in relatively short time, because release show-stoppers have not had time to accumulate. Bruno
