The postinst template uses tools from those packages.
Normally they are installed in most systems. However, this is not guaranteed. Lets make it guaranteed.
The AppData files provide descriptive data about an application, and is
typically used in application managers to display additional information to
the user. Having an AppData file is especially important for some graphical
application installers: without one, an application manager may not event
show an entry for the application. This happens for example in GNOME Software.
For the sake of completeness, this commit not only adds the AppData file to
the Flatpak build, but also to the Linux .deb and .rpm packages.
The --user-data-dir check routine shifts and removes the args. This edit is to retain the original arguments and pass to executable when finally called.
See issue #15435
libXss.so.1 was recently introduced as a dependency for correct rpm installation of vscode.
libXss.so.1 is a requirement for runtime.
this conditional check will help tooling such as yum/dnf/rpm etc ensure the proper dependency is in place at installation time and help avoid bringing in i386 dependency libraries for x86_64 architectures.
i386
libXss.so.1
x86_64
libXss.so.1()(64bit)
* use electron 1.3.4
* ATOM_SHELL_INTERNAL_RUN_AS_NODE => ELECTRON_RUN_AS_NODE
* OSS input
* update electron.d.ts
* workaround for #8708
* bump oniguruma and chokidar with custom fsevents
* build with appveyor config from master
* oops, still use ELECTRON_RUN_AS_NODE
* use electron 1.3.5
* optional fsevents
* add cat.exe to workaround output issues
* use cat for tests
* remove some now obsolete ELECTRON_NO_ATTACH_CONSOLE
* also pipe output to cat for code.sh on windows
* unset ELECTRON_RUN_AS_NODE for appveyor
* fix tfs builds?
* fix build
* fix build?
* use cat only when running tests locally
This commit adds the --user-data-dir argument which allows a custom data dir
for Chromium's user data. This is useful when running as root on Linux since
the root user does not have read or write permissions for the ~/.config/Code
dir.
Part of #3068
In Gnome and Unity desktop (and maybe some others) this can be used to open a new Code window through right click on the launcher icon and then on "New Window".
