> Ok, thanks for looking into it :)
>
> I've sent a message to the FSF (LGPL authors) to ask for a
> clarification from them.
>
> I'll have a think about whether it is at all feasible to either split
> the documentation out like that, or to build a list of copyright
> owners
> that would need to
> The documentation is copyrighted, and since there are no special
> exceptions mentioned anywhere, it's covered by LGPL like everything
> else. I now read what the license says, and I got the impression that
> if you copy the documentation, you have created a derivative work,
> and the whole work
Hi,
I don't know if you remember me, but I'm the author of the Rust binding
(https://github.com/jnqnfe/pulse-binding-rust) for PA.
I am a little uncertain about licensing with regards to my binding,
specifically whether it in any way actually does fall under the concept
of "derived
On Tue, 2018-07-10 at 13:54 +0300, Tanu Kaskinen wrote:
> On Mon, 2018-07-09 at 18:16 +0100, jnq...@gmail.com wrote:
> > On Mon, 2018-07-09 at 13:23 +0300, Tanu Kaskinen wrote:
> > > On Thu, 2018-07-05 at 23:51 +0100, jnq...@gmail.com wrote:
> > > > On Wed, 2018-07-04 at 11:46 +0300, Tanu Kaskinen
On Mon, 2018-07-09 at 13:23 +0300, Tanu Kaskinen wrote:
> On Thu, 2018-07-05 at 23:51 +0100, jnq...@gmail.com wrote:
> > On Wed, 2018-07-04 at 11:46 +0300, Tanu Kaskinen wrote:
> > > On Mon, 2018-07-02 at 17:58 +0100, jnq...@gmail.com wrote:
> > > > On Fri, 2018-06-29 at 16:06 +0300, Tanu Kaskinen
On Wed, 2018-07-04 at 11:46 +0300, Tanu Kaskinen wrote:
> On Mon, 2018-07-02 at 17:58 +0100, jnq...@gmail.com wrote:
> > On Fri, 2018-06-29 at 16:06 +0300, Tanu Kaskinen wrote:
> > > On Thu, 2018-06-28 at 04:08 +0100, jnq...@gmail.com wrote:
> > > > It's possible for patches #21, #23 and #24 to be
The internal operation_set_state function already returns early if the
new state is the same as the existing state. The attached patch extends
this to return early if already in a finalised (done/cancelled) state,
i.e. blocks attempts to re-finalise into a different state.
This helps avoid
On Fri, 2018-06-29 at 16:06 +0300, Tanu Kaskinen wrote:
> On Thu, 2018-06-28 at 04:08 +0100, jnq...@gmail.com wrote:
> > constification round #4 (pa_mainloop_api)
> >
> > 26 patches in total. I attached a zipped copy also.
> >
> > The first 19 avoid (client) API change; the final 7 do not and
On Mon, 2018-06-25 at 18:57 +0300, Tanu Kaskinen wrote:
> On Sat, 2018-06-16 at 20:01 +0100, jnq...@gmail.com wrote:
> > Is it intended that the mainloop API vtable be mutable, allowing
> > users
> > to hijack it with their own (proxy) methods, or should it and the
> > 'get_api' functions really
On Tue, 2018-06-26 at 12:15 +0300, Tanu Kaskinen wrote:
> On Tue, 2018-06-19 at 17:39 +0100, jnq...@gmail.com wrote:
> > On Mon, 2018-06-18 at 10:47 +0300, Tanu Kaskinen wrote:
> > > Your patches are based on the view that setting the error code
> > > isn't
> > > considered mutating the context
On Mon, 2018-06-18 at 10:47 +0300, Tanu Kaskinen wrote:
> On Fri, 2018-06-15 at 21:34 +0100, jnq...@gmail.com wrote:
> > On Fri, 2018-06-15 at 14:15 +0300, Tanu Kaskinen wrote:
> > > On Thu, 2018-06-07 at 05:01 +0100, jnq...@gmail.com wrote:
> > > > API constification set #3
> > > >
> > > > Some
Is it intended that the mainloop API vtable be mutable, allowing users
to hijack it with their own (proxy) methods, or should it and the
'get_api' functions really be constified?
I held off on constifying this thus far (in both patching PA itself and
in my Rust bindings) because I really wasn't
On Fri, 2018-06-15 at 14:15 +0300, Tanu Kaskinen wrote:
> On Thu, 2018-06-07 at 05:01 +0100, jnq...@gmail.com wrote:
> > API constification set #3
> >
> > Some API functions perform validation routines which may modify the
> > 'error' attribute of a context object. For API functions where the
> >
deprecated since 2009From 65c162c725302d862520ec23941fc3a188602fe6 Mon Sep 17 00:00:00 2001
From: Lyndon Brown
Date: Wed, 13 Jun 2018 20:32:21 +0100
Subject: introspection: purge autoload
deprecated since 2009
diff --git a/src/map-file b/src/map-file
index 9b6cba22..baf3799f 100644
---
On Tue, 2018-06-12 at 11:22 +0300, Tanu Kaskinen wrote:
> On Mon, 2018-05-28 at 19:37 +0100, jnq...@gmail.com wrote:
> > Hi everyone!
> >
> > Back in February I released 'binding' and 'sys' crates for using
> > pulseaudio from Rust code. I had intended to make an announcement
> > here
> > at the
API constification set #3
Some API functions perform validation routines which may modify the
'error' attribute of a context object. For API functions where the
"primary" object is not a context object, and the object holds a non-
const context pointer, this internal mechanism could be
quick patch to constify a couple of internal stream functionsFrom fdc7b0ebd82a98348d35ac1d76c937e021985a21 Mon Sep 17 00:00:00 2001
From: Lyndon Brown
Date: Thu, 7 Jun 2018 03:15:41 +0100
Subject: stream: constify internal functions
diff --git a/src/pulse/stream.c b/src/pulse/stream.c
index
On Mon, 2018-06-04 at 13:28 +0300, Tanu Kaskinen wrote:
> On Mon, 2018-05-28 at 01:49 +0100, jnq...@gmail.com wrote:
> > Constification patch set ** 1 of 2 **
> >
> > Collection of 16 patches constifying pointers in various parts of
> > the
> > API.
> >
> > This collection of patches has
Nevermind, I solved it myself - I failed to realise that I needed to
add the result of pa_rtclock_now() to the time values I was specifying
:/
___
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
Constification patch set ** 2 of 2 **
Collection of 15 patches constifying pointers in various parts of the
API.
This collection of patches have no interdependencies, they can be
applied in any order. They do *not* depend upon the 'constification
1/2' set, they can be applied independently.
Constification patch set ** 1 of 2 **
Collection of 16 patches constifying pointers in various parts of the
API.
This collection of patches has interdependencies, they must be applied
in (roughly) the given order.
These start off with constifying some core hashmap functions, which
then allows
tldr: timer events - am I doing something wrong, or is this feature
broken?
When putting together the Rust bindings a few months ago (see separate
announcement email), I created a few small test programs to test a
handful of features. One of the last features I tried to play with was
timer
at this email
address though, and bug-reports/questions/etc specific to the bindings
can be made on github (https://github.com/jnqnfe/pulse-binding-rust),
but understand that I am no PA guru :)
I do not currently have a home internet connection with my current
living situation, and manage to get online
pa_buffer_attr documentationFrom 60ce6302d2df32a3fe756ebb4e142ce09b044000 Mon Sep 17 00:00:00 2001
From: jnqnfe <jnq...@gmail.com>
Date: Thu, 31 Aug 2017 18:32:47 +0100
Subject: pa_cvolume_scale_mask: constify param
diff --git a/src/pulse/volume.c b/src/pulse/volume.c
index ffd42ecb..6b0c4b68
24 matches
Mail list logo
