Hi Eric
On 04/06/14 22:17, Eric L. wrote:
> Hi,
>
> On 4 June 2014 07:24:27 CEST, Cameron Norman wrote:
>> I think users installing this piece of software will expect it to be
>> started at boot, and we should do just that.
>
> Where I do not agree with your conclusion is that _users_ do not in
Hi,
On 4 June 2014 07:24:27 CEST, Cameron Norman wrote:
>I think users installing this piece of software will expect it to be
>started at boot, and we should do just that.
Where I do not agree with your conclusion is that _users_ do not install
software, _admins_ (aka root) do. If one user requ
On Wed, Jun 04, 2014 at 11:07:25AM +0100, Daniel Lintott wrote:
> currently BuildNotify needs to be
> started/running to access the configuration GUI.
What about this:
make the menu entry call a script that:
* checks if the BuildNotify daemon is running
* if not, starts it (as the user)
* then sta
On 04/06/14 11:40, Ansgar Burchardt wrote:
> On 06/04/2014 12:07, Daniel Lintott wrote:
>> On 04/06/14 09:53, Ansgar Burchardt wrote:
>>> BuildNotify lets you "monitor multiple continuous integration servers
>>> with customizable build notifications for all projects".
>>>
>>> I would assume it will
On 06/04/2014 12:07, Daniel Lintott wrote:
> On 04/06/14 09:53, Ansgar Burchardt wrote:
>> BuildNotify lets you "monitor multiple continuous integration servers
>> with customizable build notifications for all projects".
>>
>> I would assume it will only do useful work after configuration. If that
On 04/06/14 09:53, Ansgar Burchardt wrote:
> On 06/04/2014 07:24, Cameron Norman wrote:
>> El Tue, 3 de Jun 2014 a las 9:03 PM, Eric Lavarde escribió:
>>> Hi Daniel, On 3 June 2014 20:54:58 CEST, Daniel Lintott
>>> wrote:
>>>
>>> Hi Mentors! I'm currently packaging a notification application,
On 04/06/14 06:24, Cameron Norman wrote:
> El Tue, 3 de Jun 2014 a las 9:03 PM, Eric Lavarde escribió:
>> Hi Daniel, On 3 June 2014 20:54:58 CEST, Daniel Lintott
>> wrote:
>>
>> Hi Mentors! I'm currently packaging a notification application,
>> BuildNotify [1]. It only makes sense to star
On 04/06/14 04:55, Paul Wise wrote:
> On Wed, Jun 4, 2014 at 2:54 AM, Daniel Lintott wrote:
>
>> It only makes sense to start the application when the user logs in,
>> which can be done using the $(HOME)/.config/autostart directory or
>> adding an entry using the Startup Applications GUI.
>
> The
On 06/04/2014 07:24, Cameron Norman wrote:
> El Tue, 3 de Jun 2014 a las 9:03 PM, Eric Lavarde escribió:
>> Hi Daniel, On 3 June 2014 20:54:58 CEST, Daniel Lintott
>> wrote:
>>
>> Hi Mentors! I'm currently packaging a notification application,
>> BuildNotify [1]. It only makes sense to st
El Tue, 3 de Jun 2014 a las 9:03 PM, Eric Lavarde
escribió:
Hi Daniel,
On 3 June 2014 20:54:58 CEST, Daniel Lintott
wrote:
Hi Mentors!
I'm currently packaging a notification application, BuildNotify [1].
It only makes sense to start the application when the user logs in,
which can be done
Hi Daniel,
On 3 June 2014 20:54:58 CEST, Daniel Lintott wrote:
>Hi Mentors!
>
>I'm currently packaging a notification application, BuildNotify [1].
>
>It only makes sense to start the application when the user logs in,
>which can be done using the $(HOME)/.config/autostart directory or
>adding an
On Wed, Jun 4, 2014 at 2:54 AM, Daniel Lintott wrote:
> It only makes sense to start the application when the user logs in,
> which can be done using the $(HOME)/.config/autostart directory or
> adding an entry using the Startup Applications GUI.
There are additional dirs that the package can ins
Hi Mentors!
I'm currently packaging a notification application, BuildNotify [1].
It only makes sense to start the application when the user logs in,
which can be done using the $(HOME)/.config/autostart directory or
adding an entry using the Startup Applications GUI.
From the packaging perspecti
13 matches
Mail list logo
