- User Since
- Fri, Mar 13, 9:44 PM (2 w, 5 d)
forgot to add manpages :/
added shell completions
@dr03m I keep running into an error about missing libraries, and no matter how much I try to change pkgconfigs, pkgs, etc, I continue to get cmake errors. Sorry man, I tried lol
@dr03m instead of editing the comment, I deleted it :/
update to new upstream relese
Fri, Mar 27
@kyrios123 alright I understand now. Thanks for your response!
Thu, Mar 26
@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?
@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.
GNOME Control Center's "Color" and "Removable Devices" options worked perfectly.
Wed, Mar 25
@DataDrake I updated the summary per your request.
Revised .yml according to DataDrake's comments
Tue, Mar 24
@DataDrake updated the .yml to have the tarball as the source
change source from binary to tarball
Okay, I completely understand. I'm working on a new .yml build with rust now :)
The repository is actually mine on github. The binary comes from official site here. All I did was create a makefile for the binary and create a repo for both on github in order to make it easier to package for multiple distros. If that is against any rules though, I was unaware, and I will work on a .yml based off the upstream tarball until we get word from the devs.
@algent updated :)
add resolution to summary
@DataDrake It should have been built with the correct python version this time. Let me know if I am mistaken. I also updated the summary with the upstream change log.
Update to 4.2.0, fixes T8841
@DataDrake I volunteer as a maintainer. I have a successfully built package with the accompanying package.yml and pspec files. I'm not sure how to use arcanist though. Do I make a git repository and upload it via arc diff, or do you guys make a repository on here and I clone it and use arc diff then?
Just made a revision here