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 only do useful work after configuration. If that >>> is the case, I think setting up the autostart bits should be done by >>> BuildNotify when a user has entered something useful into the configuration. >> >> That is mostly correct... currently BuildNotify needs to be >> started/running to access the configuration GUI. > > Well, then a user has to start it once manually. Subsequent starts will > happen automatically. Okay. >> I have found that this is then saved to a file in plain text, which >> would mean I could create a debconf scenario to perform the initial >> configuration and add the appropriate autostart scripts. > > There is no per-user configuration done at package installation time. So > I don't see where you plan to use debconf. Or does BuildNotify use a > global configuration? > > Just let BuildNotify add itself to the per-user autostart once a user > has configured it. No need for debconf or anything special in the packaging. This is something I presume that will need to be handled upstream as currently it doesn't provide a simple autostart option. Regards Daniel
Attachment:
signature.asc
Description: OpenPGP digital signature