* 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
* web - first cut `yarn web` via our server
* properly pipe output
* web - remove traces of web playground
* web - remember last opened workspace for convinience
* use vscode-test-web for server less, clean up web commands
* fix comment
* fix `yarn web`
* rename to code-server
* open system browser
* code-server script: use minimist
* test resolver: use ./scripts/code-server
* integartion tests: fix code-server command name
Co-authored-by: Martin Aeschlimann <martinae@microsoft.com>
* 🆙 product
* 🆙 parcel/watcher
* 🆙 parcel/watcher
* tests - separate remote logs from others
* store server logs too
* more tweaks
* fix name
* error when 10s passed
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
