PF4Public
PF4Public
> I think this is all done because OSS is tested and developed not as a binary release, but as a folder and that's why it works now without .asar...
First of all thank you for your work to make it work (no pun intended :) ) 1. How does this PR relate to the other one? Do we need...
> VSCode requires the presence of a .git folder. […] validation fails because, instead of the commit hash, VSCode uses the version from `package.json` as a fallback I think I've...
> I think that using npm cache add is a mistake Could you add more details as to why it was a mistake? Did it fail to build a functioning...
> but can this patch be applied to current versions of applications that use perfetto? Have you tried? Unfortunately I don't have any system with musl.
I'd be happy to help if I knew how I could be of help :)
So it is either allow downloads (by default), or block all of them?
Are you sure those two patches do not negatively affect other platforms? You don't have to put a single patch into a separate folder, while holding other patches in `files`,...
> minimal versions for patches Are the files in this PR not minimal? What do you mean by "minimal"? > apply them to other chromium-based packages I won't be able...
> I mean, these patches can be ported to earlier ebuilds for electron If you're not using older versions of electron, why bother adapting patches? :D >not without problems, huh...