On 09.02.2011 15:15, Jonathan CLARKE wrote: >> As this assumption does not match reality, I am going to set up >> producing and publishing tarballs with generated files every day. Is >> that ok? > > It would certainly help. However, I often see requests from the Cfengine > team to test latest version from SVN to see if a bug is correctly fixed. > I fear this change might make this more of a hurdle, and effectively > reduce community testing on the trunk...
Fear no more :) Daily tarballs were ok testing-wise in any free software project I was involved in. >> Well, generating configure on any modern machine and building on Lenny >> is one possible workaround until aforementioned steps are taken. > > Sure, but this is pretty hard to automate, and would it not generate a > configure that relies on machine-specific parameters? If it doesn't, why > not provide one? Keeping generated files in repository is a real nuisance for a development, as they tend to desync from the source files they were generated from. > By the way, may I suggest including an "INSTALL" file, or updating > README to reflect this change? While "./configure; make" is pretty > standard and may not need documenting, I don't think it's so common to > need to generate configure (I at least have never had to, maybe it's > just me!) Many free software projects do it this way (e.g. X.org got rid of autogenerated files quite some time ago in all repositories, and explicitly tells everyone who uses git to run autogen.sh). Sure the docs need to be updated as well (and /develop page on website is changed already). _______________________________________________ Help-cfengine mailing list [email protected] https://cfengine.org/mailman/listinfo/help-cfengine
