On Mon, 22 Jul 2019 18:26:16 -0500 Troy Engel <troyengel@xxxxxxxxx> wrote: > Hi Steven, > > Can do -- right now we have the stable pinned at 2.7 which doesn't exist in > the new upstream repo, it appears the tags started with 2.8. I edited the Right. I just pushed trace-cmd-v2.7 tag to the new repo ;-) > build file locally but it's probably a dead end with 2.7 (it'll die out > naturally) - 2.7 is pinned because we have the older GTK kernelshark binary > in there, trace-cmd 2.8.x will release with KS 1.0 to supply a clean > upgrade to users. It's also a good clean break if those Python 3 patches > merge, we use the new hotness to introduce that change as well (gtk -> qt, > py2 -> py3, 1pkg -> 2pkgs). I need to push the patches. Haven't done that yet. I will tomorrow. > > For the trace-cmd-git package working off HEAD, now that trace-cmd has to Note, please use the trace-cmd-stable-v2.8 branch. HEAD for master will soon be holding development code for 2.9, and will be quite unstable. > be installed first to compile kernelshark 1.0 we need to break this apart > into two separate packages which I just haven't done yet; I have it also It's good to have the separation. We plan on working on splitting KernelShark out of the trace-cmd git repo soon. But I don't think it's a good idea to make the build of KernelShark depend on trace-cmd being installed. > edited locally in the master build file - once y'all tag KS 1.0 then we > split this single/monolithic version we've been working with out into two > packages solving the current chicken & egg problem, which then gets pushed > to stable (non-git). Based on your projections in the other email, within a > week or so but no pressure. :-) Last year I said KernelShark 1.0 will be released by August. August came and went and people asked me where KernelShark 1.0 is? I told them, I did not specify *which* August ;-) But I better not let that happen again. > > tl;dr - will do, just can't push the commits right away; we'll get the URL > changed with the packaging split/rebuild needed for trace-cmd 2.8.x / KS > 1.0 happening soon. With a trace-cmd-v2.7 tag in the main repo, can you make the update? Thanks Troy! -- Steve
|