Em 04-03-2016 09:08, Pierre Labastie escreveu: > On 04/03/2016 11:36, Fernando de Oliveira wrote: >> Em 04-03-2016 06:15, Pierre Labastie escreveu: >>> Hi, >>> >>> I am struggling through the dependency chain for LXQt, and I end up >>> needing all the dependencies for KDE-frameworks and plasma. >> I know the reason. >> >>> Of course >>> for each of KF5 and plasma, there are only a couple libraries needed, >>> but nothing is said about the dependencies for those libraries. >> You confirm that the needed libraries are stated. Don't you think you >> should rplace LXQt by KF5 and plasma in the subject, so this would not >> be misleading for someone searching in the internet? >> >> Your sentence should read: "nothing is said in in KF5 and plasma about >> their own individual dependencies". I found it, Ken found it. >> >> I think KF5 and plasma are good as they are. >> >> It is not the role of LXQt to state which are the dependencies of Plasma >> or KF5. >> >>> So it is >>> hard to know what deps are needed (I may have missed something in the >>> book), >> Perhaps scripting, instead of jhalfing? >> >>> and building LXQt is therefore very heavy (far from the >>> "lightweight" desktop advertised). >> Yes, it may be very heavyweight for jhalfs. I may have advertised that >> it is lightweight, but surely was not referring to jhalfs. >> >> >>> Does somebody know which kf5 and >>> plasma deps are really needed? >> As with other criticisms I was expecting this post. >> >> There is a simple solution: tell Bruce to divide the pages so that >> jhalfs find them. >> >> This would not be news, as many of the book is modified to solve jhalfs >> problem, when the contrary should be the correct. >> >> Sometimes I think that the project is jhalfs and the sub-projects are >> (B)LFS. >> >> Would you please try to script this part, instead of using jhalfs? >> > What I ask has nothing to do with jhalfs. Following a dependency chain > has to be done anyway! Jhalfs allows to automate that, but I do not ask > to change the book for jhalfs. In that post, I did not even ask to > change the book in any way. Of course, I could find for myself what the > dependencies are, as you and Ken did, but since you did it, and you > usually are happy to share what you find, I thought I could ask... Also, > in the book, we usually try to be explicit about dependencies, so that's > the subject of this thread. Sorry if I sounded criticizing, that was not > my aim. > > Anyway, I'll build all of plasma because I am in a hurry to tag lxqt, > and I do not have time to search which lib needs which dep.
Perhaps I am understanding now. When the LXQt instructions where written, they worked for what we had in Plasma and KF5. Now, Plasma and KF5 changed and consequently the LXQt instructions have to change in order to sync? When I did the pages, everything was there. Now, someone, perhaps you(?) needs to do it again. I never liked LXQt, because the the devs are KDE devs, each new version, new "KDE" dependencies are always introduced. From what you write, perhaps semething new has been included in "KDE" something else was modified, now the dependency chain is modified. I cannot fix. However, the list of dependencies are at: https://github.com/lxde/lxqt/wiki/Building-From-Source and do not seem to have been modified. Apologies for the posts, please. I do not like LXQt. I much prefer LXDE. If LXDE survives, I'd rather remove LXQt from the book than LXDE. Some new versions have recently been released, you saw. And a lot of development to port to gtk+3 is going on (not sure if this is a good thing or not). Very sorry with the mood of the other posts. Hope you accept my apologies. -- []s, Fernando, aka SÃsifo -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
