Commit Graph

12 Commits

Author SHA1 Message Date
Chuck
52f1332cba atom: 1.42.0 -> 1.48.0
atom-beta: 1.43.0-beta0 -> 1.49.0-beta0

This version bump includes node-gyp 3.7.0 -> 5.1.0 in Atom's
apm/package-lock.json, which, per https://github.com/nodejs/node-gyp/issues/1687
, finally allows python3 to be used instead of EOL'd python2 for
atom-package installation.
2020-06-15 17:33:14 -07:00
ysander
9922a5498b atom, atom-beta: 1.36.1 -> 1.42.0, 1.37.0-beta0 -> 1.43.0-beta0
Add shared libraries libuuid and libatk-bridge
2019-12-31 01:25:00 +01:00
worldofpeace
b1bc0645ea gdk-pixbuf: rename from gdk_pixbuf 2019-07-22 18:50:57 -04:00
volth
52f53c69ce pkgs/*: remove unreferenced function arguments 2018-07-21 02:48:04 +00:00
Patrick Hilhorst
b95b410d43
atom, atom-beta: fixed #42730
Swithed atom to use gtk3 instead of 2.
Fixed channel detection in the atom startup script.
2018-06-29 15:10:17 +02:00
Jan Tojnar
a31d98f312
tree-wide: autorename gnome packages to use dashes 2018-02-25 17:41:16 +01:00
Domen Kožar
75417d8781
atom: depend on libsecret
To support: $ atom -d
2017-12-17 15:59:05 +00:00
Benjamin Saunders
9ea655dcdd electron: 1.4.15 -> 1.6.2 2017-04-13 19:17:39 -07:00
Benno Fünfstück
a4d6e2cf16 atom: avoid using LD_PRELOAD. Fixes glibc compat issues
The wrapper for Atom was loading libraries via LD_PRELOAD, for example
libxkbfile. Now, if you installed atom via nix-env and happened to use a newer
nixpkgs for that than what your system environment is build against, you could
end up with an error like this:

```
uname: relocation error:
/nix/store/68sa3m89shpfaqq1b9xp5p1360vqhwx6-glibc-2.25/lib/libdl.so.2:
symbol _dl_catch_error, version GLIBC_PRIVATE not defined in file libc.so.6
with link time reference
```

This happens because atom calls the `uname` executable from the system to
determine the platform. Because that inherits the `LD_PRELOAD` environment
variable, so the libxkbfile library that the `atom` wrapper was build against
is loaded into `uname`. But since `atom` comes from `nix-env`, the `libxkbfile`
it was built with might be compiled against a newer version of `glibc` than
`uname`, which comes from the system, was! Having two versions of glibc loaded
into the same processes results in chaos.

To fix this, we avoid setting `LD_PRELOAD` and instead use patchelf to set the
correct RPATH. RPATH is not inherited by child processes, so the above issue
can no longer occur.

The only small complication here is that the library that actually loads
libxkbfile is not the atom binary itself, but a node extension that atom uses.
So instead of setting the RPATH on `atom` only, we also set the `rpath` on all
node extensions (`*.node`) the output.
2017-03-18 01:51:36 +01:00
Kirill Boltaev
bccd75094f treewide: explicitly specify gtk and related package versions 2016-09-12 18:26:06 +03:00
Nikolay Amiantov
daa8ba26c9 atomEnv: use makeSearchPathOutput 2016-04-25 13:24:40 +03:00
Nikolay Amiantov
6185f74531 atom, electron, vscode: split dependencies to atomEnv
fixes #14890
2016-04-22 16:10:51 +02:00