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 a polkit policy that is read when fs-admin invokes `dd` via
`pkexec` after trying to write into a restricted location. By specifying
`auth_admin_keep`, we are telling the polkit daemon to not prompt users
for a password again if they have already escalated privileges recently.
Co-Authored-By: Rafael Oleza <rafeca@github.com>
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.
This change adds automation for producing nightly Atom releases using
VSTS CI. Most of the changes are just slight modifications to Atom's
existing build scripts to produce another build channel and publish
those artifacts in a way that can be installed and updated when new
releases are available.
