[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] gnu: Add libunique.

From: ng0
Subject: Re: [PATCH] gnu: Add libunique.
Date: Mon, 01 Aug 2016 14:46:31 +0000

Hello Fabian Harfert,

I see your contribution did not receive any further reaction.
Did it just disappear in the work-in-progress branches/folders you have,
or do you have no further intentions to work on it for whatever reasons
it may be (time, resources, …)?

I'd like to move this contribution of yours over the "finishing line",
tell me if you like to pick up work on it or prefer someone else to
finish it.


Leo Famulari <address@hidden> writes:

> On Fri, Feb 19, 2016 at 09:10:44PM +0100, Fabian Harfert wrote:
> Thanks for the patch!
>> * gnu/packages/patches/libunique-gdbus.patch: New file.
>> * gnu/packages/patches/libunique-remove-G_CONST_RETURN.patch: New file.
> Can you give the context of these patches?
> I see there are newer versions available:
> Perhaps a more recent release would not require the patches?
> In any case, remember you have to register the patches in
> (dist_patch_DATA). There's a recent example in 4e58a402.
>> * gnu/packages/glib.scm (libunique): New variable.
> [...]
>> +    (synopsis "Library for writing single instance application")
> How about "Library for writing single instance applications"?
>> +    (description
>> +     "Libunique is library providing a mechanism to allow only one running
>> +instance of an application.")
> I think we should steal Debian's description:
> "Libunique is a library for writing single instance application. If you
> launch a single instance application twice, the second instance will
> either just quit or will send a message to the running instance.
> Libunique makes it easy to write this kind of applications, by providing a
> base class, taking care of all the IPC machinery needed to send messages
> to a running instance, and also handling the startup notification side."
> [...]

♥Ⓐ  ng0
Current Keys:
For non-prism friendly talk find me on

reply via email to

[Prev in Thread] Current Thread [Next in Thread]