Refs https://github.com/microsoft/vscode/issues/212494
When using the default ANGLE gl/gles backend, v1.90 attempts
to get display refresh rate for vsync from an internal implementation
instead of using the gl extension EGL_CHROMIUM_sync_control,
this eventually ends up loading display info from XRandr and chromium
attempts to set a label for the data from the shipped resource pak
file that is not accessible to the gpu process triggering a SIGTRAP
in ui::ResourceBundle::GetSharedInstance.
This software is not a plain text editor, and it's definitely not a file manager.
Advertising compatibility with such overrides default OS handlers on many distributions, unnecessarily.
* RPM spec: Use standard macros for paths/name
- Once `@@NAME@@` is replaced into the spec file as the `Name:`,
it can be referenced with the RPM macro `%{name}`
- The installation directories corresponding to `/usr/bin/` and
`/usr/share/` are defined in the RPM macros `%{_bindir}` and
`%{_datadir}`
Co-authored-by: Raymond Zhao <7199958+rzhao271@users.noreply.github.com>
Co-authored-by: Robo <hop2deep@gmail.com>
Create the `/usr/bin/code` symlink during %install
so that the package owns and manages it.
Also, make it relative (for better relocatability).
Co-authored-by: Raymond Zhao <7199958+rzhao271@users.noreply.github.com>
* Commit non-py files
* Finish porting calculate and merge scripts for rpm
* Switch back to ts, add binaryDir
* Pass in app path
* Trim string before splitting
* Move files, apply PR feedback
* Add deps to exclude and crashpad handler dep
* polish
When lauching with `env POSIXLY_CORRECT=y code [...]`, VSCode creates two directories named `-m` and `700`. This is because the order of arguments, in a POSIX strict environment, matters.
* fix: use clang and libcxx from chromium
* chore: add flags for Link-Time Optimization
libcxx builds from upstream are built with LTO, avoiding these
flags will cause miscompiles
* chore: add lto flags to compilation units
* linux - remove `--no-sandbox` flag
We should not disable sandbox on Linux.
We only added this to support running on Kernel <= 3.8 where setuid sandbox is used.
* fix ci
* add some docs
This should not be longer than 80 characters/line. The last two lines belong to /usr/share/doc/code/README.Debian
Also it should not start with "Visual Studio Code is" but rather with "This is"
Please refer to the Debian Developer Manual.
