Re: [libvirt] seek alternative way of compiling historical version

On Sun, Apr 02, 2017 at 08:05:01AM -0400, Dan wrote: I haven't heard of any project ever that would do anything like this. Is it that much more complicated to do: git checkout v2.0.0; git clean -fxd; git submodule update In most cases only the first command needs to be done anyway. Depends what you want to test. For some things it's enough to have a rule, for example that you must not change API call numbers. For others there are tests. If tests start failing, something went wrong. If you have pdwtags installed, usually from the 'dwarves' package, there is also test for remote structures (that they don't change), but mostly people need to be careful while writing and reviewing code. Funny fact, back then it was libvir! not libvirt. Hence the mailing list address. Well it also didn't do much, I presume. I can't say for sure, though, I'm just guessing it from the documentation. Isn't this how all projects start? =)