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

Bug#641812: ITP: qt-solutions -- libqtsingleapplication0: support for starting applications only once



Control: retitle 641812 ITP: qt-solutions -- libqtsingleapplication0: support for starting applications only once
Control: owner 641812 !
Control: blocks 775456 by 641812

On Sat, Sep 17, 2011 at 11:12:09AM +0200, Sune Vuorela wrote:
> On Saturday 17 September 2011 01:45:41 you wrote:

> > An alternative would be to merge the relevant code into Sankore's main
> > source, and tagging this obsoleted code as a candidate to be replaced as
> > soon as possible. Is that solution better?
> 
> Given that the QtSolution code is more example code than library code, I think 
> that this is a better solution, yes, and it is also my recommendation to other 
> users of QtSolution code.

Not sure it’s a good idea to provide multiple convenience code copies in
many places, but I may be missing something obvious.

> My next suggestion would be to convert the bits that aren't in Qt proper into 
> proper libraries and use them and package them as such.

My intent, while taking over this ITP, is simply to provide
qtsingleapplication as a start (as needed by sankore, #775456).

If other modules are worth packaging/sharing, it should be pretty easy
to enlarge the build process for them. I’ll soon push a repository in
alioth as debian-edu/pkg-team/qt-solutions.git, but don’t mind moving it
to collab-maint or anywhere people wish once other modules are wanted.

> The things that might be reasonable as actual libraries would be
>  - qtsoap (even though it is a quite bad soap implementation)
>  - qtsingleapplication
>  - qtcolor*
>  - qtpiemenu
>  - qtmmlwidget
>  - qtiocompressor
>  - qtservice
>  - qtlockedfile
> 
> But it requires work to get these to a standard where they are worth using as 
> libraries.

Regards

David

Attachment: signature.asc
Description: Digital signature


Reply to: