From: Michael Albinus <michael.albinus@gmx.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
Jan Moringen <jan.moringen@uni-bielefeld.de>
Subject: Re: Inclusion of dbus-proxy
Date: Thu, 26 Aug 2010 12:09:31 +0200 [thread overview]
Message-ID: <nqmxs9ofc4.fsf@alcatel-lucent.com> (raw)
In-Reply-To: <87eidnd7cq.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 24 Aug 2010 23:32:53 +0200")
Chong Yidong <cyd@stupidchicken.com> writes:
> It looks interesting, and I'd like to add it; the question is whether to
> add it to the main Emacs tarball, or to elpa.gnu.org. If it is very
> likely that many other parts of Emacs will make use of this package as a
> piece of basic "infrastructure", it should go into the tarball.
Honestly, I don't know. It adds a convenience layer for access to
applications via D-Bus; such a layer is offered by other D-Bus language
bindings as well.
OTOH, it cannot be regarded as the default library for communicationg
with other applications via D-Bus, because there are applications which
do not offer introspection data. In this case, the low level functions
must still be used.
> If in doubt, we can add it to elpa.gnu.org for now.
>
> What do you think?
Maybe adding to elpa.gnu.org is OK for now. If we see the majority of
packages, which need D-Bus, are using dbus-proxy.el, we shall move it to
Emacs core.
Best regards, Michael.
next prev parent reply other threads:[~2010-08-26 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 22:03 Inclusion of dbus-proxy Jan Moringen
2010-08-22 14:47 ` joakim
2010-08-22 16:20 ` Michael Albinus
2010-08-22 21:04 ` Jan Moringen
2010-08-23 13:23 ` Kevin Rodgers
2010-08-23 15:44 ` Michael Albinus
2010-08-24 2:03 ` Jan Moringen
2010-08-24 19:50 ` Michael Albinus
2010-08-24 21:32 ` Chong Yidong
2010-08-24 23:59 ` Tom Tromey
2010-08-26 10:09 ` Michael Albinus [this message]
2010-08-25 3:24 ` Jan Moringen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nqmxs9ofc4.fsf@alcatel-lucent.com \
--to=michael.albinus@gmx.de \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=jan.moringen@uni-bielefeld.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).