Package.yml update
cleaned up builddeps
git needed for pulling wsjtx patched hamlib from wsjtx-dev git
textinfo asciidoc needed for building of manual, without package will not build.
We're at v6.2.0. now...
No abi files generated?
Well, it seems it was a cable problem. I don't know how it is possible it was a cable, but I changed it and since then I don't have this issue. But it is only one day of testing right now...
Fixed the permissions
Update to godot 3.2.1
Update to nuget 5.6.0.6532
Ah, thanks for letting me know.
let us globals handle this, we are working at graph-tool already with the libboost update
Fixed 80 column in summary, otherwise LGTM. Thanks!
You need to add: Depends on D8566 to the summary
Forgot to mention this goes with D8566 but that should be fairly obvious.
I'm not happy with this, chances are I'll revisit, but with a more generic update instead of a full on change with splash.
LGTM, thanks!
Update test plan description
@kyrios123 alright I understand now. Thanks for your response!
but why base the release off of the SDK? According to the upstream github releases, SDK releases are very scattered and do not release for every version, and in turn, do not give users performance improvements such as those mentioned in T8849 for a while.
Change to font-jetbrainsmono-ttf
Add proper rundeps now
@DataDrake I'm not sure if I understand you correctly. The mesa drivers has to incorporate changes from upstream vulkan? If so, I see what you mean about rebasing on a standard release being pointless. However, couldn't a more up-to-date vulkan-loader lib still increase performance along with mesa, or allow for more to date features (such as ray tracing, since it was introduced in 1.2.135)? Or could mesa use the newly introduced features from updated spec with an outdated vulkan-loader SDK?
In D8511#137574, @JoshStrobl wrote:If they add an OTF dist, we won't have to perform any shenanigans.
But they don't so that's kinda moot.
If they add an OTF dist, we won't have to perform any shenanigans.
Why are we patterning this instead of just calling the package font-jetbrainsmono-ttf when all this ships is ttf files?
@sethfl These are just headers. The benefits of any changes are only realized when the libraries that use them are updated. The most important of which being Mesa which hasn't incorporated these changes yet.
@JoshStrobl I understand leaving this to the core team, but why base the release off of the SDK? According to the upstream github releases, SDK releases are very scattered and do not release for every version, and in turn, do not give users performance improvements such as those mentioned in T8849 for a while. Wouldn't it be better to release the SDK as a vulkan-devel package and rebase the vulkan package on the standard release in order to give end users performance improvements faster? Just kinda wondering 🤔
rebuilt against master branch.
Update to v1.0.5
Fix MAINTAINERS.md
This needs to be against master branch not your arc patch branch. Please make sure you are properly squashing your commits and basing your work against master.
LGTM, thanks!
Otherwise LGTM
They don't have an SDK release out. Please leave this to @kyrios123 and Core Team, thanks.