<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Ohh,...<br>
<br>
should read more careful, or stop watching videos next to it.^^ ;)<br>
<br>
Am 15.01.2014 23:48, schrieb Andrey Kozhevnikov:<br>
</div>
<blockquote cite="mid:52D7104B.4000903@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
we're talking about dbus interfaces, not apis :)<br>
<br>
<div class="moz-cite-prefix">On 16.01.2014 04:47, Gabriel Böhme
wrote:<br>
</div>
<blockquote cite="mid:52D70FF6.3010306@googlemail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">I think DBUS is not restricted at
all as far as I know, Bernd wrote the following some days ago:<br>
<br>
<pre wrap=""><i>This comment was about one specific DBus API (PackageKit), which will be
made unavailable to 3rd party applications soon to prevent unrequested
sideloading of RPM packages. An API designed for use by 3rd party
applications for this task will be made available.
DBus APIs generally are available to you if you have the right to acces
them from your application without raising the applications
privileges. PackageKit (hopefully) is the one big exception there at the
moment. We're trying to create additional documentation on stability of
DBus APIs to help you to avoid using an API which will still change a lot.</i>
</pre>
Gabriel.<br>
<br>
<br>
<br>
Am 15.01.2014 23:43, schrieb Andrey Kozhevnikov:<br>
</div>
<blockquote cite="mid:52D70F05.40906@gmail.com" type="cite">D-Bus
interfaces not allowed for harbour. <br>
And you can use everything you want if dont need to go to
harbour :) <br>
<br>
On 16.01.2014 04:35, Matthias Fehring wrote: <br>
<blockquote type="cite">Hello, <br>
<br>
I have a question concerning the harbour rules and the
currently allowed stuff. <br>
<br>
My application (<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://ocnews.buschmann23.de">http://ocnews.buschmann23.de</a>)
consists of two executable files. One is the frontend, the
other one is a daemon/engine. Both are communicating through
D-Bus, the daemon/engine is also started on request through
D-Bus. <br>
<br>
Now the harbour rules seems only to allow one executable per
package. How to go around these problem? Creating two
packages? <br>
<br>
The other thing is the D-Bus interface of the daemon/engine.
The new rpm validator in the SDK says, that it is not
allowed to install files in /usr/share/dbus-1/interfaces and
/usr/share/dbus-1/services. <br>
<br>
Is there a solution for that or can it currently not
published through Jolla Store when it uses it's own D-Bus
interface? <br>
<br>
<br>
Best greetings <br>
Matthias <br>
_______________________________________________ <br>
SailfishOS.org Devel mailing list <br>
</blockquote>
<br>
_______________________________________________ <br>
SailfishOS.org Devel mailing list <br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SailfishOS.org Devel mailing list</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SailfishOS.org Devel mailing list</pre>
</blockquote>
<br>
</body>
</html>