`gnome-keyring` is necessary to run the secret service itself. A KDE-equivalent is not (yet) available. Without its daemon service, libsecret cannot store any secrets.
Put it in recommends so that it is installed by default (majority of use-cases)
Atom is not install-able on Ubuntu Groovy because of outdated dependencies as described in #21422
This fixes and updates Atom dependencies after investigation with @DeeDeeG
Some dependencies are not required by Electron anymore, some packages are unavailable/outdated and need alternatives
Some dependencies are less strict and can be a suggestion or recommendation. For details see bugreport #21422
These overrides are very outdated.
(Haven't been updated since the day they were added, back in 2014.)
Even with these applied, Lintian still prints many warns/errors.
I think no-one has been running Lintian
against the .deb package for a while now.
Python is only needed for apm --> npm --> node-gyp.
(For building Atom packages that include native C/C++ code.)
The rest of Atom/apm works 100%, even with no Python installed.
With Python 2 soon to be dropped from the Debian/Ubuntu repos,
having a hard dependency on `python` or `python2` is a problem.
None of the other OSes/platforms have an install-time requirement of
having Python on the system, so this is in line with Atom packaging
for the other platforms.
This is used by fs-admin to invoke `pkexec` and escalate privileges to
write into restricted locations.
Co-Authored-By: Rafael Oleza <rafeca@github.com>
This was added at the request of a user in #7066 with no reasoning
behind it as far as I can tell. Since the current Atom binary doesn't
depend on this library it should be removed.
This is another dependency that came from the old WebUpd8 package in
f431bb6, however this one doesn't seem like it was necessary in the
first place, or if it wass the `atom` binary no longer requires it.
The `gconf2` and `gconf-service` dependencies originally were added in
f431bb6 from the WebUpd8 version of the Atom .deb file. It looks like
although they seemed to work for the most part, they were likely
incorrect originally, and certainly are now.
This commit switches these over to the `libgconf-2-4 | libgconf2-4`
dependency listed in electron-installer-debian and Chrome.
* libgcrypt11-dev on debian is a dammy file "shortcut" to libgcrypt20 . so to make possible to install atom on debian testing version we should add on depends ** libgcrypt20.
libgcrypt20 has backward compatibility to libgcrypt11 .
** libgcrypt20 is comfortable with debian unstable/testing , and ubuntu 14.04TLS .
* libgcrypt11 (without -dev) not exists on debian testing and makeing bugs with atom deb file .
