Date: | Wed, 04 Nov 2020 07:51:11 -0500 |
---|---|
From: | Stan Cox <scox@xxxxxxxxxx> |
Subject: | [DynInst_API:] testsuite releases request |
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.0Source0: 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. |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | [DynInst_API:] [dyninst/dyninst] e5a888: Add note about minimum elfutils version (#912), noreply |
---|---|
Next by Date: | Re: [DynInst_API:] testsuite releases request, thaines . astro |
Previous by Thread: | Re: [DynInst_API:] setting dyninst probes in firefox, mxz297 |
Next by Thread: | Re: [DynInst_API:] testsuite releases request, thaines . astro |
Indexes: | [Date] [Thread] |