@watpi sorry for not replying sooner, for some reason it doesn't look like I'm getting email notifications.

I have submitted a patch for inclusion in the repo (D3990). If this patch is good, and the triage team want me to, I would be happy to step up to maintain this package.

I have successfully built opam through solbuild but I have to force make to build serially (by passing -j1). I have opened an issue in the opam github repo to ask if parallel builds are possible (https://github.com/ocaml/opam/issues/3585).

Sorry, I was meant to get round to try and package this. Last time I tried I ran into issues because the opam build scripts makes external network requests.

@DataDrake thanks!

Is there a possibility of reconsidering this package for inclusion? I don't agree with the ocamlbrew arguement that was mentioned previously.

@Nikki1993 no one is being hostile, you must understand that it is quite tiring to see people repeating the same point over and over.

@pwfraley along with what @tristan957 said, I would like to add a little more.

@selfus no problem, we all want the latest and greatest software, but it can come at a cost sometimes :)

@selfus I don't think that is fair to say.

@joebonrichie Good work!

@tristan957 this is more of a roadmap for Solus, not for general packages to be included in the repo that might not effect many users.

Just had a thought, and instead of copying the entire directory like an idiot, i've just made a symlink to the folder. While this is not a clean fix, it works as a temp fix for me.

I would like to add that a simple cp -r ~/.config/'Code - OSS' ~/.config/Code makes the errors in the dev tools go and the info banner stop appearing, so im guessing it is just an issue with the folder name?

In T3915#69297, @sunnyflunk wrote:

Need to use arcanist for patches now, see:

https://solus-project.com/articles/packaging/submitting-a-package/en/
https://www.youtube.com/watch?v=rlPnHjUBpJ8