ehrm,

how is it expected to work, please?

It checkouts read-only working copy from github here. No cloning from git.lxde.org. And mainly - url specified for lxde.org is not an url of "developer" checkout (unable to commit again).
Should I take it as a read only tool for packagers/end users?

Just because I find to work with many independent repositories one by one as a mission impossible ;)

Also how is that jhbuild "install" tree used in testing? I'd expect issued with QSettings here (but maybe is this part reworked already) as QSettings expected hardcoded path to /etc/... (different per distro).

So should I set all these env vars as in jhbuildrc + PATH + LD_LIBRARY_PATH and then run xephyr (or something similar) with lxqt-session? Or is there something easier?

thanks,
petr

On 06/03/14 18:57, PCMan wrote:
> Hello,
> I just applied the patches provided by Veeti.
> Now the whole lxqt can be built with jhbuild.
>
> Please use the new jhbuild config files here.
> https://github.com/lxde/jhbuild
>
> If you don't use jhbuild, everything still works as before and was not affected.
> Thank Veeti for the patches.
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Lxde-list mailing list
> Lxde-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxde-list