{"id":23390272,"url":"https://github.com/diixo/dbus","last_synced_at":"2025-04-08T14:19:48.865Z","repository":{"id":160164393,"uuid":"350455579","full_name":"diixo/dbus","owner":"diixo","description":"Release dbus-library from http://dbus.freedesktop.org/releases/dbus. Contains API functions used to communicate with the DBus message bus. Patched for capicxx-dbus-runtime.","archived":false,"fork":false,"pushed_at":"2022-05-04T13:30:09.000Z","size":2359,"stargazers_count":2,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-02-14T10:43:29.969Z","etag":null,"topics":["capicxx-dbus-runtime","commonapi-dbus","dbus","dbus-api","dbus-cxx","libdbus"],"latest_commit_sha":null,"homepage":"","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/diixo.png","metadata":{"files":{"readme":"README","changelog":"ChangeLog","contributing":"CONTRIBUTING.md","funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS","dei":null,"publiccode":null,"codemeta":null}},"created_at":"2021-03-22T18:53:37.000Z","updated_at":"2024-05-18T16:06:42.000Z","dependencies_parsed_at":null,"dependency_job_id":"7bd937b1-91a8-4658-9ac1-08d8336103cd","html_url":"https://github.com/diixo/dbus","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/diixo%2Fdbus","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/diixo%2Fdbus/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/diixo%2Fdbus/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/diixo%2Fdbus/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/diixo","download_url":"https://codeload.github.com/diixo/dbus/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247856545,"owners_count":21007621,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["capicxx-dbus-runtime","commonapi-dbus","dbus","dbus-api","dbus-cxx","libdbus"],"created_at":"2024-12-22T03:29:24.457Z","updated_at":"2025-04-08T14:19:48.846Z","avatar_url":"https://github.com/diixo.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"Sections in this file describe:\n - introduction and overview\n - low-level vs. high-level API\n - version numbers\n - options to the configure script\n - ABI stability policy\n\nIntroduction\n===\n\nD-Bus is a simple system for interprocess communication and coordination.\n\nThe \"and coordination\" part is important; D-Bus provides a bus daemon that does things like:\n - notify applications when other apps exit\n - start services on demand\n - support single-instance applications\n\nSee http://www.freedesktop.org/software/dbus/ for lots of documentation, \nmailing lists, etc.\n\nSee also the file CONTRIBUTING.md for notes of interest to developers\nworking on D-Bus.\n\nIf you're considering D-Bus for use in a project, you should be aware\nthat D-Bus was designed for a couple of specific use cases, a \"system\nbus\" and a \"desktop session bus.\" These are documented in more detail\nin the D-Bus specification and FAQ available on the web site.\n\nIf your use-case isn't one of these, D-Bus may still be useful, but\nonly by accident; so you should evaluate carefully whether D-Bus makes\nsense for your project.\n\nSecurity\n==\n\nIf you find a security vulnerability that is not known to the public,\nplease report it privately to dbus-security@lists.freedesktop.org\nor by reporting a freedesktop.org bug that is marked as\nrestricted to the \"D-BUS security group\" (you might need to \"Show\nAdvanced Fields\" to have that option).\n\nOn Unix systems, the system bus (dbus-daemon --system) is designed\nto be a security boundary between users with different privileges.\n\nOn Unix systems, the session bus (dbus-daemon --session) is designed\nto be used by a single user, and only accessible by that user.\n\nWe do not currently consider D-Bus on Windows to be security-supported,\nand we do not recommend allowing untrusted users to access Windows\nD-Bus via TCP.\n\nNote: low-level API vs. high-level binding APIs\n===\n\nA core concept of the D-Bus implementation is that \"libdbus\" is\nintended to be a low-level API. Most programmers are intended to use\nthe bindings to GLib, Qt, Python, Mono, Java, or whatever. These\nbindings have varying levels of completeness and are maintained as\nseparate projects from the main D-Bus package. The main D-Bus package\ncontains the low-level libdbus, the bus daemon, and a few command-line\ntools such as dbus-launch.\n\nIf you use the low-level API directly, you're signing up for some\npain. Think of the low-level API as analogous to Xlib or GDI, and the\nhigh-level API as analogous to Qt/GTK+/HTML.\n\nVersion numbers\n===\n\nD-Bus uses the common \"Linux kernel\" versioning system, where\neven-numbered minor versions are stable and odd-numbered minor\nversions are development snapshots.\n\nSo for example, development snapshots: 1.1.1, 1.1.2, 1.1.3, 1.3.4\nStable versions: 1.0, 1.0.1, 1.0.2, 1.2.1, 1.2.3\n\nAll pre-1.0 versions were development snapshots.\n\nDevelopment snapshots make no ABI stability guarantees for new ABI\nintroduced since the last stable release. Development snapshots are\nlikely to have more bugs than stable releases, obviously.\n\nConfiguration \n===\n\ndbus could be build by using autotools or cmake. \n\nWhen using autotools the configure step is initiated by running ./configure \nwith or without additional configuration flags. dbus requires GNU Make\n(on BSD systems, this is typically called gmake) or a \"make\" implementation\nwith compatible extensions.\n\nWhen using cmake the configure step is initiated by running the cmake \nprogram with or without additional configuration flags. \n\nConfiguration flags\n===\n\nWhen using autotools, run \"./configure --help\" to see the possible\nconfiguration options and environment variables.\n\nWhen using cmake, inspect README.cmake to see the possible\nconfiguration options and environment variables.\n    \nAPI/ABI Policy\n===\n\nNow that D-Bus has reached version 1.0, the objective is that all\napplications dynamically linked to libdbus will continue working\nindefinitely with the most recent system and session bus daemons.\n\n - The protocol will never be broken again; any message bus should \n   work with any client forever. However, extensions are possible\n   where the protocol is extensible.\n\n - If the library API is modified incompatibly, we will rename it \n   as in http://ometer.com/parallel.html - in other words, \n   it will always be possible to compile against and use the older \n   API, and apps will always get the API they expect.\n\nInterfaces can and probably will be _added_. This means both new\nfunctions and types in libdbus, and new methods exported to\napplications by the bus daemon.\n\nThe above policy is intended to make D-Bus as API-stable as other\nwidely-used libraries (such as GTK+, Qt, Xlib, or your favorite\nexample). If you have questions or concerns they are very welcome on\nthe D-Bus mailing list.\n\nNOTE ABOUT DEVELOPMENT SNAPSHOTS AND VERSIONING\n\nOdd-numbered minor releases (1.1.x, 1.3.x, 2.1.x, etc. -\nmajor.minor.micro) are devel snapshots for testing, and any new ABI\nthey introduce relative to the last stable version is subject to\nchange during the development cycle.\n\nAny ABI found in a stable release, however, is frozen.\n\nABI will not be added in a stable series if we can help it. i.e. the\nABI of 1.2.0 and 1.2.5 you can expect to be the same, while the ABI of\n1.4.x may add more stuff not found in 1.2.x.\n\nNOTE ABOUT STATIC LINKING\n\nWe are not yet firmly freezing all runtime dependencies of the libdbus\nlibrary. For example, the library may read certain files as part of\nits implementation, and these files may move around between versions.\n\nAs a result, we don't yet recommend statically linking to\nlibdbus. Also, reimplementations of the protocol from scratch might\nhave to work to stay in sync with how libdbus behaves.\n\nTo lock things down and declare static linking and reimplementation to\nbe safe, we'd like to see all the internal dependencies of libdbus\n(for example, files read) well-documented in the specification, and\nwe'd like to have a high degree of confidence that these dependencies\nare supportable over the long term and extensible where required.\n\nNOTE ABOUT HIGH-LEVEL BINDINGS\n\nNote that the high-level bindings are _separate projects_ from the\nmain D-Bus package, and have their own release cycles, levels of\nmaturity, and ABI stability policies. Please consult the documentation\nfor your binding.\n\nBootstrapping D-Bus on new platforms\n===\n\nA full build of D-Bus, with all regression tests enabled and run, has some\ndependencies which themselves depend on D-Bus, either for compilation or\nfor some of *their* regression tests: GLib, dbus-glib and dbus-python are\ncurrently affected.\n\nTo avoid circular dependencies, when bootstrapping D-Bus for the first time\non a new OS or CPU architecture, you can either cross-compile some of\nthose components, or choose the build order and options carefully:\n\n* build and install D-Bus without tests\n  - do not use the --enable-modular-tests=yes configure option\n  - do not use the --enable-tests=yes configure option\n* build and install GLib, again without tests\n* use those versions of libdbus and GLib to build and install dbus-glib\n* ... and use those to install dbus-python\n* rebuild libdbus; this time you can run all of the tests\n* rebuild GLib; this time you can run all of the tests\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdiixo%2Fdbus","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdiixo%2Fdbus","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdiixo%2Fdbus/lists"}