The build and release procedures on fedora and rhel are tied to upstream
releases. So for example current fedora and rhel do this in
dyninst.spec (rpm build file)
%define __testsuite_version 10.1.0
Source0:
https://github.com/dyninst/dyninst/archive/v%{version}/dyninst-%{version}.tar.gz
Source1:
https://github.com/dyninst/testsuite/archive/v10.1.0/testsuite-%{__testsuite_version}.tar.gz
The tar ball is grabbed and cached locally. Any patches to be applied
plus the spec file are checked into a release engineering git
repository. This is built in a build farm using a standard "root
environment."
I still use the 10.1.0 testsuite as that is the last release available.
Just a small request. Going forward could a testsuite release be
matched with a dyninst release? I am carrying forward a bunch of
testsuite patches to get the 10.1.0 testsuite to build.
_______________________________________________
Dyninst-api mailing list
Dyninst-api@cs.wisc.edu
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api
