X/Qt2 opie integration (patches included)

X/Qt2 opie integration (patches included)

[Bernhard Guillon]

Hi all,
here [1] [2] [3] are my efforts to integrate X/Qt2 into opie. Everything 
works fine for SIMpad.  Can we put that into dev branch?

best regrads
Bernhard Guillon

1 http://linuxtogo.org/gowiki/Angstrom/XQt/playground
2 http://bugs.openembedded.net/show_bug.cgi?id=4582
3 http://bugs.openembedded.net/show_bug.cgi?id=4603

Re: X/Qt2 opie integration (patches included)

[Koen Kooi]

On 03-10-2008 20:19, Bernhard Guillon wrote:
> Hi all,
> here [1] [2] [3] are my efforts to integrate X/Qt2 into opie. Everything
> works fine for SIMpad. Can we put that into dev branch?
>
> best regrads
> Bernhard Guillon
>
> 1 http://linuxtogo.org/gowiki/Angstrom/XQt/playground
> 2 http://bugs.openembedded.net/show_bug.cgi?id=4582
> 3 http://bugs.openembedded.net/show_bug.cgi?id=4603

NACK!

+do_install() {
[..]
+	install -d ${D}/home/root
+	install -m 0600 .blackboxrc ${D}/home/root

A package NEVER EVER touches $HOME. NEVER! I wish ascii could produces 
some bigger capitals that blink and have baseballbats to get the point 
across, but sadly it can't.

Imagine I don't log in as root and fire up packagekit to install that 
packages. I don't get the .blackboxrc, but the root user suddenly has 
his .blackboxrc overwritten without notice.

So:

A package NEVER EVER touches $HOME. NEVER!

${sysconfdir} exists for a reason.

regards,

Koen

Re: X/Qt2 opie integration (patches included)

[Bernhard Guillon]

Koen Kooi schrieb:
>
> NACK!
>
> +do_install() {
> [..]
> +    install -d ${D}/home/root
> +    install -m 0600 .blackboxrc ${D}/home/root
>
> A package NEVER EVER touches $HOME. NEVER! I wish ascii could produces 
> some bigger capitals that blink and have baseballbats to get the point 
> across, but sadly it can't.
>
> Imagine I don't log in as root and fire up packagekit to install that 
> packages. I don't get the .blackboxrc, but the root user suddenly has 
> his .blackboxrc overwritten without notice.
>
> So:
>
> A package NEVER EVER touches $HOME. NEVER!
>
> ${sysconfdir} exists for a reason.
>
Ok, I added a second version of the patch to the bugtracker which 
implements your suggestion.

I did use ${HOME} in the first version because it is the standard 
location for blackbox configuration [1].

Is there any way for a clean implementation to put the config to the 
standard location? With e.g postinstall? I don't like the idea of not 
using a standard location but I agree that hardcode to /home/root can 
cause trouble.


best regards
Bernhard Guillon

1 
http://blackboxwm.sourceforge.net/BlackboxDocumentation/BlackboxConfiguration#location

Re: X/Qt2 opie integration (patches included)

[Bernhard Guillon]

Any obstacles left? Else I would like to ask if some of you can please 
commit it [2] [3] to .dev branch.

best regards
Bernhard Guillon

1 http://linuxtogo.org/gowiki/Angstrom/XQt/playground
2 http://bugs.openembedded.net/show_bug.cgi?id=4582
3 http://bugs.openembedded.net/show_bug.cgi?id=4603

Bernhard Guillon schrieb:
> Koen Kooi schrieb:
>>
>> NACK!
>>
>> +do_install() {
>> [..]
>> +    install -d ${D}/home/root
>> +    install -m 0600 .blackboxrc ${D}/home/root
>>
>> A package NEVER EVER touches $HOME. NEVER! I wish ascii could 
>> produces some bigger capitals that blink and have baseballbats to get 
>> the point across, but sadly it can't.
>>
>> Imagine I don't log in as root and fire up packagekit to install that 
>> packages. I don't get the .blackboxrc, but the root user suddenly has 
>> his .blackboxrc overwritten without notice.
>>
>> So:
>>
>> A package NEVER EVER touches $HOME. NEVER!
>>
>> ${sysconfdir} exists for a reason.
>>
> Ok, I added a second version of the patch to the bugtracker which 
> implements your suggestion.
>
> I did use ${HOME} in the first version because it is the standard 
> location for blackbox configuration [1].
>
> Is there any way for a clean implementation to put the config to the 
> standard location? With e.g postinstall? I don't like the idea of not 
> using a standard location but I agree that hardcode to /home/root can 
> cause trouble.
>
>
> best regards
> Bernhard Guillon
>
> 1 
> http://blackboxwm.sourceforge.net/BlackboxDocumentation/BlackboxConfiguration#location 
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: X/Qt2 opie integration (patches included)

[Koen Kooi]

On 07-10-2008 13:20, Bernhard Guillon wrote:
> Any obstacles left? Else I would like to ask if some of you can please
> commit it [2] [3] to .dev branch.

I still dislike a single package handling so many different things *and* 
containing config files for other packages.


> best regards
> Bernhard Guillon
>
> 1 http://linuxtogo.org/gowiki/Angstrom/XQt/playground
> 2 http://bugs.openembedded.net/show_bug.cgi?id=4582
> 3 http://bugs.openembedded.net/show_bug.cgi?id=4603
>
> Bernhard Guillon schrieb:
>> Koen Kooi schrieb:
>>>
>>> NACK!
>>>
>>> +do_install() {
>>> [..]
>>> + install -d ${D}/home/root
>>> + install -m 0600 .blackboxrc ${D}/home/root
>>>
>>> A package NEVER EVER touches $HOME. NEVER! I wish ascii could
>>> produces some bigger capitals that blink and have baseballbats to get
>>> the point across, but sadly it can't.
>>>
>>> Imagine I don't log in as root and fire up packagekit to install that
>>> packages. I don't get the .blackboxrc, but the root user suddenly has
>>> his .blackboxrc overwritten without notice.
>>>
>>> So:
>>>
>>> A package NEVER EVER touches $HOME. NEVER!
>>>
>>> ${sysconfdir} exists for a reason.
>>>
>> Ok, I added a second version of the patch to the bugtracker which
>> implements your suggestion.
>>
>> I did use ${HOME} in the first version because it is the standard
>> location for blackbox configuration [1].
>>
>> Is there any way for a clean implementation to put the config to the
>> standard location? With e.g postinstall? I don't like the idea of not
>> using a standard location but I agree that hardcode to /home/root can
>> cause trouble.
>>
>>
>> best regards
>> Bernhard Guillon
>>
>> 1
>> http://blackboxwm.sourceforge.net/BlackboxDocumentation/BlackboxConfiguration#location
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: X/Qt2 opie integration (patches included)

[Bernhard Guillon]

Koen Kooi schrieb:
> On 07-10-2008 13:20, Bernhard Guillon wrote:
>> Any obstacles left? Else I would like to ask if some of you can please
>> commit it [2] [3] to .dev branch.
>
> I still dislike a single package handling so many different things 
> *and* containing config files for other packages.
>
It contains three different things:

-a config for blackbox which may is useless without xqtlauncher. it puts 
the taskbar from the bottom to the top of the screen.

-a .desktop(opie compliant) file for xkbd which is useless without 
xqtlauncher

-xqtlauncher skripts
--startxqt
    checks if x/qt2 is already running, creates a run file set up 
environment and starts x/qt2
--startxqt-wrapper
    starts startxqt in bg and also starts the wm (in this stage of 
development only blackbox)
--xqtlauncher
    takes an X11 application as argument e.g. xkbd
    check if this application is available
    check if xqt2 is running and starting it
    atomate count of the applications running +1
    run application
    atomate count of the applications running -1
    if application counter <= 0 kill xqt2

The symlink for xqtlauncher is needed because opie only takes the first 
exec argument of the .desktop file to decide if the application is 
already running and starts one application only once (discussed with 
bluelightning). The alternatives to this are creating shell script 
wrappers or change the code in opie. But changing the code in opie is no 
option for me.

For a useful xqt2 xkbd is currently needed because typing on opies 
keyboard kills xqt2 except of this it is quite stable on my simpad.

I can split the package.
For that I need some advice for spliting and naming of the packages.

What do you think about:

xqtlauncher-blackbox-config.bb
xqtlauncher-xkbd-desktop.bb
xqtlauncher.bb having the above as rdepends?

or
xqtlauncher-blackbox-config.bb
xqtlauncher-xkbd-desktop.bb
xqtlauncher.bb no depends except X/Qt2
and a task-xqtlauncher.
With this we could provide support for different window managers later. 
Currently only blackbox is supported.

or same as above but
xqt2-xqtlauncher-foo-bar.bb

best regards
Bernhard Guillon

Re: X/Qt2 opie integration (patches included)

[Koen Kooi]

On 07-10-2008 14:33, Bernhard Guillon wrote:
> Koen Kooi schrieb:

> What do you think about:
>
> xqtlauncher-blackbox-config.bb
> xqtlauncher-xkbd-desktop.bb
> xqtlauncher.bb having the above as rdepends?
>
> or
> xqtlauncher-blackbox-config.bb
> xqtlauncher-xkbd-desktop.bb
> xqtlauncher.bb no depends except X/Qt2
> and a task-xqtlauncher.
> With this we could provide support for different window managers later.
> Currently only blackbox is supported.
>
> or same as above but
> xqt2-xqtlauncher-foo-bar.bb

Option 2 seems nice.

regards,

Koen

Re: X/Qt2 opie integration (patches included)

[Bernhard Guillon]

Koen Kooi schrieb:
> On 07-10-2008 14:33, Bernhard Guillon wrote:
>> Koen Kooi schrieb:
>
>> What do you think about:
>>
>> xqtlauncher-blackbox-config.bb
>> xqtlauncher-xkbd-desktop.bb
>> xqtlauncher.bb having the above as rdepends?
>>
>> or
>> xqtlauncher-blackbox-config.bb
>> xqtlauncher-xkbd-desktop.bb
>> xqtlauncher.bb no depends except X/Qt2
>> and a task-xqtlauncher.
>> With this we could provide support for different window managers later.
>> Currently only blackbox is supported.
>>
>> or same as above but
>> xqt2-xqtlauncher-foo-bar.bb
>
> Option 2 seems nice.
>
It took a while but here [1] it is :)

Please have a look at it and comment.

best regards
Bernhard Guillon

[1] http://bugs.openembedded.net/show_bug.cgi?id=4603
[2] http://bugs.openembedded.net/show_bug.cgi?id=4582
[3] http://bugs.openembedded.net/show_bug.cgi?id=4861

Re: X/Qt2 opie integration (patches included)

[Bernhard Guillon]

Bernhard Guillon schrieb:
> It took a while but here [1] it is :)
>
> Please have a look at it and comment.
>
Any obstacles left? Else I would like to ask if some of you can please 
commit it [1] [2] [3] to .dev branch.

best regards
Bernhard Guillon

>
> [1] http://bugs.openembedded.net/show_bug.cgi?id=4603
> [2] http://bugs.openembedded.net/show_bug.cgi?id=4582
> [3] http://bugs.openembedded.net/show_bug.cgi?id=4861

Re: X/Qt2 opie integration (patches included)

[Graeme Gregory]

On Tue, 2008-10-07 at 14:33 +0200, Bernhard Guillon wrote:
> For a useful xqt2 xkbd is currently needed because typing on opies 
> keyboard kills xqt2 except of this it is quite stable on my simpad.
> 
Many years ago I fixed this, its because Xqt tries to instantiate some
unicode codec which we don't build into our qte. It fails, doesn't check
for the null response then segfaults.

Cant remember what the fix was, but it wasn't too difficult.

Graeme