translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
application
    gapplication2.68.3
    QmSYyomotHhkmCnGFJMDGRaF7gQpeA6cCHhxNHRzLeATSa
    5drUAamntJxuMXTfCQmtsZWAnoVghN
      QmSYyomotHhkmCnGFJMDGRaF7gQpeA6cCHhxNHRzLeATSa
      5drUAamntJxuMXTfCQmtsZWAnoVghN

      • Details
      • Run
      • Files
      • History
        • Website

          https://wiki.gnome.org/Projects/GLib

          License

          • LGPL 2.1

          Environment

          linux

          Architecture

          x86-64

          gapplication is a commandline implementation of the client-side of the org.freedesktop.Application interface as specified by the freedesktop.org Desktop Entry Specification.

          gapplication can be used to start applications that have DBusActivatable set to true in their .desktop files and can be used to send messages to already-running instances of other applications.

          It is possible for applications to refer to gapplication in the Exec line of their .desktop file to maintain backwards compatibility with implementations that do not directly support DBusActivatable.

          gapplication ships as part of GLib.

          Versions

          • 2.54.1

          • 2.68.3

          Related

          • maintainer

            occam

          • within

            library

            glib2

          • packaged with

            application

            gtester

          • packaged with

            application

            gobject-query

          • packaged with

            application

            gio

          • packaged with

            application

            gresource

          • packaged with

            application

            gio-querymodules

          • packaged with

            application

            glib-compile-schemas

          • packaged with

            application

            glib-compile-resources

          • packaged with

            application

            gsettings

          • packaged with

            application

            gdbus

          • packaged with

            application

            gtester-report

          • packaged with

            application

            glib-genmarshal

          • packaged with

            application

            glib-mkenums

          • packaged with

            application

            gdbus-codegen

          • packaged with

            application

            glib-gettextize

          DependenciesHelp

          This section shows a list of objects the current object is dependent upon in order to be used.

          For dependencies that are only relevant as part of the build or runtime of the object, it is best to describe those local to those sections.

          • library

            zlib

            1.x

          • library

            ffi

            3.x

          • collection

            util-linux

            2.x

          • library

            elf

            0.x

          • language

            python

            3.x

          • library

            pcre

            8.x

          RunHelp

          This section tracks information useful to describing how to run this object.

          Command

          • /usr/bin/gapplication

          Run Environment

          • linux
          • x86-64

          InstallationHelp

          Objects have a set of files that comprise that object, as seen in the Files tab. When an object is built, they have a set of files that are the result of that build. In each case, these sets of files are the ones that are accessible within a virtual machine when running the object.

          This section describes how those files are accessible and visible to that machine. When a virtual machine is created, the data is always accessible read-only within a particular mounted directory. However, applications may expect to be located at particular directories. This section allows one to place files in different directories when the virtual machine is launched.

          There are two types of access. One is a link where the file is not copied from its original location. Instead, it creates what is called a symbolic link which is a "shortcut" that acts like a normal file but allows the actual data to be in a different directory. The other type is a traditional copy which copies the data explicitly to the provided destination. This takes more time, but the copy can be modified, unlike the read-only link type.

          ActionSourceDestinationSummary
          Linkusr/lib/usr/lib

          N/A

          Linkusr/include/usr/include

          N/A

          Linkusr/share/usr/share

          N/A

          Linkusr/bin/usr/bin

          N/A

          No files will be installed.

          Share

          • URL

            Copy
          • Embed Link

            Copy
          • QR Code

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        Confirm
        Do you wish to proceed?

        Confirm message?