Fix screencopy shm release and PipeWire version check#4217
Conversation
|
This is maybe not the most appropriate place to have this discussion but i couldn't help but notice you opened roughly 12 PRs in the past 5 hours. |
rust-lang/rust#156077 might be instructive. NB I am not passing any judgement, other than agreeing that 12 PRs in 5 hours, with no prior contribution, is anomalous behaviour. I know people who go on coding binges like this though, and I haven't looked at any of this code. Anyway, that |
if you'd look at the contribution history this statement is false, rather than speculating and insisting threats, it may be valuable to actually go read before saying
|
I maintain a private fork and I have took it beyond myself not to contribute upstream a couple months ago due to a disagreement between members in the unofficial discord server over topics unrelated to development which resulted in a timeout when the initial conversation was induced by a development request. Hence, I took it upon myself to fix issues and maintain my own version rather than contributing because of the hostile actions of the team. It also seems the owner has become rather preoccupied with other medial tasks including school and his research not being able to handle the backlog of issues and features which caused me furthermore to fix such issues on my own time. In inception, I admired this project but the discord server despite being unofficial has become rather propaganda making me deterred from contribution |
ah, glad to know these weren't just vibecoded in the timeframe between each PR request. |
Summary
pw_check_library_version, which is missing from older libpipewire runtimes, by reading and parsingpw_get_library_versioninstead.readyon success or afterfailedon failed/abandoned copies.Issues
Testing
cargo fmt --all -- --checkcargo test -q pipewire_version_is_at_leastcargo check --message-format=shortcargo check