2014-02-06 PCMan <pcman...@gmail.com>:
> On Thu, Feb 6, 2014 at 4:33 AM, Petr Vaněk <p...@yarpen.cz> wrote:
>
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> hi again,
>>
>> I'm just interested how it looks with "new infrastructure".
>> Are all repositories migrated to lxde infrastructure already?
>>
> Not yet, but I already set them up and will finish them this week
> hopefully.
>
>
>> Should I commit into lxde git instead of github? (key needs to be sent)
>>
> When I confirm that the new repos work, maybe we can start using it?
>
>
>> Is it all mirrorred to gihub?
>>
> Not yet, sorry.
>
>
>> Is there something official to build all-in-one?
>>
> If you mean cmake, no.
> A contributor mentioned jhbuild previously and I tried it earlier, but it
> seems to be hard to configure. Theoratically it should supports cmake and
> autotools at the same time and is very suitable for our task, but I don't
> know how to use it.
>
I did a CMakelists.txt for the cmake projects, and it was working at some
point in time. It is slow, in part because it just calls cmake on each
subproject, and each subrepo has to do discovery of needed libraries etc.
In razor the master cmake-project did that.
build_all.sh is pretty difficult to use. Having just changed job, I
installed lxqt on a new machine, and it took me a long time. Some of the
problems encountered:
- I had to change the building order. lxqt-notification (I think) now
depends on libfm-qt, so pcman-qt has to be built before lxqt-notification
- lxmenu-data requires an automake version of 1.10 or 1.11. I have
1.12.something installed, so I hand to remove that check from autogen.sh
- I need to set up PKG_CONFIG_PATH to look in /usr/local/lib/pkgconfig
- I need to set up LIBRARY_PATH to include /usr/local/lib
I think, if someone comes along (a prospective developer perhaps), and
tries to clone and build lxqt, odds are that he or she will back away.
For the kde build tool, I read some docs about it but haven't figure out
> how to use it with our project. :-(
> So currently I'm using the build_all.sh script.
> Docs about how to build cmake & autotools projects simultaneously and
> configure the libraries correctly is missing. I just cannot find them
> anywhere. Maybe I can ask for help on the cmake mailing list. I can do it.
>
>
>> Redmine?
>>
> I tried to get in contact with our current web admin for the donated
> server space, but he did not reply my mail yet.
> Guess that he's busy with his real life.
> Outside the internet, the volunteers all have their real lives and I can
> understand that quite well.
> I'd suggest that we wait for a little more time. Really sorry for the
> inconvenience.
>
>
>>
>> FYI I tried to update my semi-functional lxqt installation but handling
>> set of sub-repositories is a nightmare.
>>
>> Yeah, I noticed that. Git submodule is not as good as it's advertised.
> Please try the following command.
> > git submodule update --init --remote --rebase
> This can save some time for you and does the work most of the time.
> Indeed, a single huge repo is really easier to handle in many areas.
>
I'm also in favor of one repo. I think the way it is now, is very
cumbersome. One problem: If you want to get lxqt from github, you do:
git clone https://github.com/lxde/lxde-qt.git
cd lxde-qt
git submodule init
git submodule update
git submodule foreach checkout master
git submodule foreach pull --rebase
:-)
- as pr. the wiki-guide, and if you then do:
git status
you get:
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
modified: libfm (new commits)
modified: liblxqt (new commits)
modified: libqtxdg (new commits)
modified: lximage-qt (new commits)
modified: lxinput-qt (new commits)
modified: lxmenu-data (new commits)
modified: lxqt-common (new commits)
modified: lxqt-session (new commits)
modified: lxsession (new commits)
modified: obconf-qt (new commits)
modified: pcmanfm-qt (new commits)
no changes added to commit (use "git add" and/or "git commit -a")
Which is confusing. There should not be anything with a freshly cloned
project. The problem is, AFAICT, that when you do a commit & push in a
subrepo, you have to commit and push in the master repo as well, to make
the master repo point to the new commit in the subrepo. Right now the
master repo on github points to old commits in some of the subrepos.
Not a huge problem, easy to fix, but it shows that Git submodule is not
really being used as it should. IMHO we might just as well have a bunch of
unrelated git repos, and a script to clone them all. But I agree with Petr
that one repo is strongly preferable.
However, as the project grows, we'll need to split them someday, and it's
> easier to do if we do it earlier.
> I admitted that sometimes I missed the one-repo setup when git submodule
> does not work as well as expected. :-(
> Do you have other ideas?
>
I think we should take the pain of subrepos when we need it and not before.
Also, even then, it should not be necessary to have one repo pr. module. We
could start with having the autotools projects in one repo. And then
perhaps, if we really need to, maybe split the cmake-projects into a repo
with libraries and a repo with modules or whatever.
- br. Chr.
>
>
Also I found older razor installation on one of my machines and I can
>> confirm few things: lxqt desktop component is much faster than razor's.
>> Razor's session seems more "seamless" than a lxde's. Just my 2c ;)
>>
>> I'm working on making it more seamless now and already had some progress.
> At least the themes are integrated.
> Besides, the configuration tools will be working again soon.
>
>
>> BTW it seems there is still place for our effort. See the first place in
>> "most favorited qt apps" list:
>> http://qt-apps.org/index.php?xsortmode=high
>>
> and it reminds me one thing - I'd still prefer to start using adjective
>> "classic" instead of "lightweight" as word lightweight seems yet another
>> buzzword.
>>
>> Agree! I just noticed this, too.
> Compared with QML stuff, animations, Gnome shell, and KDE plasma,
> "classic" is a more suitable term for us.
> Lightweight is more subjective. Regarding to the design, ours is more
> "classic".
>
> Cheers!
>
>
>> cheers,
>> petr
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>> Comment: GPGTools - http://gpgtools.org
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iQEcBAEBAgAGBQJS8qAnAAoJEC8yRjM4uE2tAPgH/2ww/EB9FOzLI2jtGOqHju0T
>> Bok6kt+3B4WjMLO6OmlfaEXtz0PQdbO9/2RmOAFHkuDwij37t5hf77RDXJm53dwb
>> LQDO9YCwAzLS7VfjiekB8iyFnMqg9wq9DZNErUyzBqyXER/A/biyY+C1b04t8+uw
>> 9bKACzP7IE7trAmfrErliJNGNDqh4vx2C4NVz9h12EVMhmWPM27IM2t7rqrDahIh
>> 0RDhUSG3WlRn4nJm075wFlqItAID+Y8xlzxgJu+yz9w2GnnGqkABVXNtlI2/vq/Y
>> IPE5Ao8VNdCiPIrJIkujQZi9LUhuhOtDYDkwPwcL+QtC8tXrkgKlvlqLO42jjp4=
>> =ikrE
>> -----END PGP SIGNATURE-----
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Managing the Performance of Cloud-Based Applications
>> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
>> Read the Whitepaper.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Lxde-list mailing list
>> Lxde-list@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/lxde-list
>>
>
> --
> --
> You received this message because you are subscribed to the Google
> Groups "Razor-qt" group.
> For more options, visit this group at
> http://groups.google.com/group/razor-qt?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Razor-qt" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to razor-qt+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
