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.
* 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 .
Linux icons are now only copied for build process, not for install
process. They should be ignored for all platforms except RPM package
build on Linux.
I realize the debian package build depends on this. Although it
probably won't break anything, I would rather implement a solution
that doesn't change the behavior of the debian installer.
This is so that the atom.desktop file will be able to find the
"atom" icon when requested. This adds the dependency of ImageMagick
to convert atom.png to varying resolutions, although, only during
the rpm build process (not during actual install). So the result
is ultimatly no different for the end user.
Also, fixed an absolute path from the rpm build process and made
it relative. It was hardcoded in the spec file to
"/tmp/atom-build/Atom/*", so builds that were made elsewhere would
have broken when attempting to package into an rpm. Now rpm packaging
should work from a build made anywhere. Also needed to modify
script/mkrpm so that it copies the build files in such a way that
they can more easily be dealt with in the spec file in a relative
way.
