You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I needed to do a maintenance release of an older product build. The fix required a change to a 3rd party library that was pulled from conan center. This required me to vendor the recipe. Because I wanted to change as little as possible, I wanted to get the exact recipe used for the recipe revision I was locked to. I was able to recreate this from the cache of my previous package version, but it is missing some stuff (e.g. testing). It would have been useful if I could have looked up the git commit corresponding to that recipe revision so I could browse the repository at that commit. Seems like you could capture that at the time the recipe is published.
The text was updated successfully, but these errors were encountered:
Hi @rconde01 thanks for your suggestion. I can't guarantee that anything will come out of it, but I plan to take a look at this next week to understand the feasibility of having a feature such as the one you describe :)
Given that each version get's a different revision and does not match the source code because of the hooks reduction of the conandata.yml so it only "kinda" matches.
I am pretty sure this is not possible without other backend changes... since we do not build a commit that ever exists on GItHub that SHA would be meaning less but it could add to the importance of the other changes
What is your problem/feature request?
I needed to do a maintenance release of an older product build. The fix required a change to a 3rd party library that was pulled from conan center. This required me to vendor the recipe. Because I wanted to change as little as possible, I wanted to get the exact recipe used for the recipe revision I was locked to. I was able to recreate this from the cache of my previous package version, but it is missing some stuff (e.g. testing). It would have been useful if I could have looked up the git commit corresponding to that recipe revision so I could browse the repository at that commit. Seems like you could capture that at the time the recipe is published.
The text was updated successfully, but these errors were encountered: