|
|
|
|
|
by Aurornis
212 days ago
|
|
> https://gitlab.com/evlaV/holo-PKGBUILD So to summarize: Valve provides source code for what they distribute, in compliance with the GPL, but this person went on a personal crusade to demand they open up their private GitLab to the world? There appears to be some interesting history here, but this takes the cake as the weirdest README I've ever seen in a git repo. The writing is impenetrably wordy and filled with excessive bolding and parentheticals. It goes completely off track and turns into an extremely long rant that implores the reader to "abstain from procreation", among other things. There are hundreds of links and hundreds of quotes mixed into long-winded sections about the author's self-importance. Does anyone have a link to a more down to earth, less self-important, and more importantly concise explanation of what's going on? |
|
(In other words, even if you download a tarball of all SteamOS code, you cannot build it, because the build script insists on downloading source code from a Valve-internal remote, instead of looking for it locally.)
So to fix this, the author of this repo did two things: they created public mirrors of all individual git repos that are referenced by the PKGBUILD scripts (presumably by extracting the tarballs from Valve's release and running git init/add/commit/push), and then they created a "master" repo (linked here) that has only the PKGBUILDs, which the author fixed so they reference their own public mirrors instead of Valve's internal GitLab repos. See [1], for example, which contains the build instructions for the Steam Deck's DSP driver. The referenced git repository ([2]) is an inofficial mirror of Valve's internal repo, created from the source code release from the Valve website.
So no, it's not a "personal crusade" to demand Valve open up their "private GitLab to the world". It's a serious grievance about Valve releasing an "open-source" software that cannot actually be built from source, and a request for Valve to provide a public GitLab mirror themselves, such that their PKGBUILD scripts will actually work.
I agree that the author has a confusing writing style, but I do understand their frustrations and concerns.
[1]: https://gitlab.com/evlaV/jupiter-PKGBUILD/-/blob/master/stea...
[2]: https://gitlab.com/evlaV/valve-hardware-audio-processing