There's been build problems for a few months now. https://forums.freebsd.org/threads/is-vscode-broken.88334/I was wondering if anyone know why vscode is no longer available as a package?
Has absolutely nothing to do with it.it would be toooooo heavy build dependency
Nonsense. Builds are mostly "atomic", in other words the packages get build from a snapshot of the ports tree at any given time. The ports tree the build cluster uses isn't updated while the builds are running.is updated too often that build cluster cannot build it within each updates and no pkg is created, thus vscode cannot be started building.
Actually, it has ... see also my PR 270565.Has absolutely nothing to do with it.
This might be a misunderstanding, I think what he meant was that too often in a bulk run, electron would have to be rebuilt because the version changed from the previous bulk run.Nonsense. Builds are mostly "atomic", in other words the packages get build from a snapshot of the ports tree at any given time. The ports tree the build cluster uses isn't updated while the builds are running.
If you're talking about electron (and not vscode itself), I would like to disagreeIt's not a heavy build
+1. This is what I mean.If you're talking about electron (and not vscode itself), I would like to disagree
If the dependency itself is not updated, it is not deleted and used.Would it be possibly useful if old packages are kept until the new ones build successfully, or they can't because of dependencies?