Re: [blfs-dev] dependencies for LXQt

[Bruce Dubbs]

Pierre Labastie wrote:

On 05/03/2016 18:08, Bruce Dubbs wrote:

Pierre Labastie wrote:


I realize I should have read again the thread starting at
http://lists.linuxfromscratch.org/pipermail/blfs-dev/2015-November/031384.html.
Sorry
for duplicate.

I think we should create a ticket and discuss there what to do (after
release). I'll do that unless somebody speaks up


Lets just discuss here.  First please re-summarize the issues as you see them.



Let me summarize:
According to the present instructions in the book, the above thread, and this
one, LXQt depends on:
- kwindowsystem (from KF5) for liblxqt, for lxqt-policykit (actually, since
liblxqt is required, that dep should not be mentioned at the lxqt-policykit
page), and for lxqt-runner
- kguiaddons and solid (from KF5), for lxqt-panel,
- libkscreen (from Plasma) for lxqt-config.

However, the specific dependencies of those libraries are not given in the
book, only the whole set of dependencies for KF5 and Plasma.

Bruce's proposition is to separate those libraries from the KF5 or plasma
page. But as Fernando remarked in the first thread, next version of LXQt might
have different dependencies among the FK5 and plasma libraires. This already
occured when updating to LXQt-0.10 in November. The former version of LXQt
only depended on kwindowsystem and kguiaddons.


OK, I see you tagged lxqt.  I have not built that yet.  I'm going to do a 
test build without kf5/plasma and just build the minimum needed.  I'll 
place the kf5/plasma libraries using LXQT_PREFIX=/opt/lxqt.  If it works 
properly, I'll add those pages in the lxqt section.

-
Right now the following packages remain that need tags:

networking/netprogs/samba.xml:
networking/netprogs/cifsutils.xml:
networking/mailnews/fetchmail.xml:
networking/mailnews/mutt.xml:
networking/netutils/wicd.xml:

server/mail/exim.xml:
server/mail/dovecot.xml:

server/major/proftpd.xml:
server/major/bind.xml:
server/major/vsftpd.xml:
server/other/xinetd.xml:

x/installing/x7driver-vmware.xml:

xsoft/other/ekiga.xml:

I think you said you'll do exim and dovecot.  I can do most of the rest 
but take whatever else you want to do.


I don't have any Windows systems, so I'll mark samba and cifsutils as 
lfs79_built unless we get someone to volunteer to test.


I also don't have vmware, so it will also be lfs79_built unless we have 
someone who can test it.


ekiga builds and comes up, but I don't really know how to adequately 
use/test.  I'm inclined to just tag checked anyway.


I'll note that I was able to test/tag transmission.  It worked, but I was 
not impressed.  I tried to download a 4G iso and it was taking forever. 
After 5-10 minutes is had only downloaded about 1%.  I killed it and a 
simple wget was getting about 13MB/s on the same file.


  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] dependencies for LXQt

[Pierre Labastie]

On 05/03/2016 18:08, Bruce Dubbs wrote:
> Pierre Labastie wrote:
> 
>> I realize I should have read again the thread starting at
>> http://lists.linuxfromscratch.org/pipermail/blfs-dev/2015-November/031384.html.
>> Sorry
>> for duplicate.
>>
>> I think we should create a ticket and discuss there what to do (after
>> release). I'll do that unless somebody speaks up
> 
> Lets just discuss here.  First please re-summarize the issues as you see them.
> 
> Note, I have to leave for a couple of hours in about 30 minutes.
> 
>   -- Bruce
> 

Let me summarize:
According to the present instructions in the book, the above thread, and this
one, LXQt depends on:
- kwindowsystem (from KF5) for liblxqt, for lxqt-policykit (actually, since
liblxqt is required, that dep should not be mentioned at the lxqt-policykit
page), and for lxqt-runner
- kguiaddons and solid (from KF5), for lxqt-panel,
- libkscreen (from Plasma) for lxqt-config.

However, the specific dependencies of those libraries are not given in the
book, only the whole set of dependencies for KF5 and Plasma.

Bruce's proposition is to separate those libraries from the KF5 or plasma
page. But as Fernando remarked in the first thread, next version of LXQt might
have different dependencies among the FK5 and plasma libraires. This already
occured when updating to LXQt-0.10 in November. The former version of LXQt
only depended on kwindowsystem and kguiaddons.

regards
Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] dependencies for LXQt

[Bruce Dubbs]

Pierre Labastie wrote:


I realize I should have read again the thread starting at
http://lists.linuxfromscratch.org/pipermail/blfs-dev/2015-November/031384.html. 
Sorry
for duplicate.

I think we should create a ticket and discuss there what to do (after
release). I'll do that unless somebody speaks up


Lets just discuss here.  First please re-summarize the issues as you see them.

Note, I have to leave for a couple of hours in about 30 minutes.

  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] dependencies for LXQt

[Pierre Labastie]

On 04/03/2016 22:43, Fernando de Oliveira wrote:
> Em 04-03-2016 18:09, Bruce Dubbs escreveu:
>> Pierre Labastie wrote:
>>> On 04/03/2016 17:16, Ken Moffat wrote:
 On Fri, Mar 04, 2016 at 12:10:46PM -0300, Fernando de Oliveira wrote:
> Em 04-03-2016 09:08, Pierre Labastie escreveu:
 (trimming severely)
>> On 04/03/2016 11:36, Fernando de Oliveira wrote:
>>> Em 04-03-2016 06:15, Pierre Labastie escreveu:
 Does somebody know which kf5 and
 plasma deps are really needed?
>> 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.
>
> 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.
>
 The last time I built lxqt, the only KF5 deps it needed were:

 extra-cmake-modules

 kwindowsystem (I built those two before liblxqt)

 kguiaddons (I built that before libstatgrab)

 I can see that I also built oxygen-icons from kde4, and the qt5
 version of polkit-qt.

  From what I remember, it really required openbox (I had thought
 other 'box WMs might pass muster).

 ĸen
>>> Thanks,
>>>
>>> Actually, as I said, I built all of kf5 and plasma. I found a small (but
>>> annoying, because libksysguard was not applied the fix) bug in the plasma
>>> instructions, (see commit r17061), so hopefully, making the book better.
>>>
>>> Otherwise, the LXQT build went smoothly, so I think the instructions are
>>> good. I have built openbox, lxdm and sddm. I still have to test that now.
>>>
>>> To Fernando, I understood you hadn't understood my first post. That's why
>>> I explained. I'm glad we agree (I do not like LXQt either, for the same
>>> reasons as you...).
>>
>> I've read the thread.  I have to admit that I haven't built LXQt. 
>> Looking through the instructions, I don't really like the way the
>> kf5/plasma dependencies are presented.
>>
>> From what I can see, the following are needed:
>>
>> From KF5: kwindowsystem, kguiaddons, solid
>> Form Plasma: libkscreen
>>
>> These in turn have dependencies.  Looking at the CMakeLists.txt files in
>> those packages tells me that they need extra-cmake-modules and the xcb
>> libraries in xorg.  libkscreen has an optional dependency of doxygen.
>>
>> Solid has optional dependencies media-player-info (not in the book),
>> udisks2, and upower.
>>
>>
>> My preference would be to add pages for  kwindowsystem, kguiaddons,
>> solid, and libkscreen to the book in the LXQt section and add a note
>> that they are also built as a part of KF5 and (or plasma for libkscreen)
>> and do not need to be rebuilt if those multiple package installs have
>> been made.
>>
>> If needed I can test it by just renaming /opt/kf5.  (Another good reason
>> for building in /opt).
> 
> Second time you propose.
> 
> Please, make it readable. I always fail.
> 
> Thanks.
> 

I realize I should have read again the thread starting at
http://lists.linuxfromscratch.org/pipermail/blfs-dev/2015-November/031384.html. 
Sorry
for duplicate.

I think we should create a ticket and discuss there what to do (after
release). I'll do that unless somebody speaks up

Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] dependencies for LXQt

[Fernando de Oliveira]

Em 04-03-2016 18:09, Bruce Dubbs escreveu:
> Pierre Labastie wrote:
>> On 04/03/2016 17:16, Ken Moffat wrote:
>>> On Fri, Mar 04, 2016 at 12:10:46PM -0300, Fernando de Oliveira wrote:
 Em 04-03-2016 09:08, Pierre Labastie escreveu:
>>> (trimming severely)
> On 04/03/2016 11:36, Fernando de Oliveira wrote:
>> Em 04-03-2016 06:15, Pierre Labastie escreveu:
>>> Does somebody know which kf5 and
>>> plasma deps are really needed?
> 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.

 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.

>>> The last time I built lxqt, the only KF5 deps it needed were:
>>>
>>> extra-cmake-modules
>>>
>>> kwindowsystem (I built those two before liblxqt)
>>>
>>> kguiaddons (I built that before libstatgrab)
>>>
>>> I can see that I also built oxygen-icons from kde4, and the qt5
>>> version of polkit-qt.
>>>
>>>  From what I remember, it really required openbox (I had thought
>>> other 'box WMs might pass muster).
>>>
>>> ĸen
>> Thanks,
>>
>> Actually, as I said, I built all of kf5 and plasma. I found a small (but
>> annoying, because libksysguard was not applied the fix) bug in the plasma
>> instructions, (see commit r17061), so hopefully, making the book better.
>>
>> Otherwise, the LXQT build went smoothly, so I think the instructions are
>> good. I have built openbox, lxdm and sddm. I still have to test that now.
>>
>> To Fernando, I understood you hadn't understood my first post. That's why
>> I explained. I'm glad we agree (I do not like LXQt either, for the same
>> reasons as you...).
> 
> I've read the thread.  I have to admit that I haven't built LXQt. 
> Looking through the instructions, I don't really like the way the
> kf5/plasma dependencies are presented.
> 
> From what I can see, the following are needed:
> 
> From KF5: kwindowsystem, kguiaddons, solid
> Form Plasma: libkscreen
> 
> These in turn have dependencies.  Looking at the CMakeLists.txt files in
> those packages tells me that they need extra-cmake-modules and the xcb
> libraries in xorg.  libkscreen has an optional dependency of doxygen.
> 
> Solid has optional dependencies media-player-info (not in the book),
> udisks2, and upower.
> 
> 
> My preference would be to add pages for  kwindowsystem, kguiaddons,
> solid, and libkscreen to the book in the LXQt section and add a note
> that they are also built as a part of KF5 and (or plasma for libkscreen)
> and do not need to be rebuilt if those multiple package installs have
> been made.
> 
> If needed I can test it by just renaming /opt/kf5.  (Another good reason
> for building in /opt).

Second time you propose.

Please, make it readable. I always fail.

Thanks.

-- 
[]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

Re: [blfs-dev] dependencies for LXQt

[Bruce Dubbs]

Pierre Labastie wrote:

On 04/03/2016 17:16, Ken Moffat wrote:

On Fri, Mar 04, 2016 at 12:10:46PM -0300, Fernando de Oliveira wrote:

Em 04-03-2016 09:08, Pierre Labastie escreveu:

(trimming severely)

On 04/03/2016 11:36, Fernando de Oliveira wrote:

Em 04-03-2016 06:15, Pierre Labastie escreveu:

Does somebody know which kf5 and
plasma deps are really needed?

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.

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.


The last time I built lxqt, the only KF5 deps it needed were:

extra-cmake-modules

kwindowsystem (I built those two before liblxqt)

kguiaddons (I built that before libstatgrab)

I can see that I also built oxygen-icons from kde4, and the qt5
version of polkit-qt.

 From what I remember, it really required openbox (I had thought
other 'box WMs might pass muster).

ĸen

Thanks,

Actually, as I said, I built all of kf5 and plasma. I found a small (but
annoying, because libksysguard was not applied the fix) bug in the plasma
instructions, (see commit r17061), so hopefully, making the book better.

Otherwise, the LXQT build went smoothly, so I think the instructions are
good. I have built openbox, lxdm and sddm. I still have to test that now.

To Fernando, I understood you hadn't understood my first post. That's why
I explained. I'm glad we agree (I do not like LXQt either, for the same
reasons as you...).


I've read the thread.  I have to admit that I haven't built LXQt.  Looking 
through the instructions, I don't really like the way the kf5/plasma 
dependencies are presented.


From what I can see, the following are needed:

From KF5: kwindowsystem, kguiaddons, solid
Form Plasma: libkscreen

These in turn have dependencies.  Looking at the CMakeLists.txt files in 
those packages tells me that they need extra-cmake-modules and the xcb 
libraries in xorg.  libkscreen has an optional dependency of doxygen.


Solid has optional dependencies media-player-info (not in the book), 
udisks2, and upower.



My preference would be to add pages for  kwindowsystem, kguiaddons, solid, 
and libkscreen to the book in the LXQt section and add a note that they 
are also built as a part of KF5 and (or plasma for libkscreen) and do not 
need to be rebuilt if those multiple package installs have been made.


If needed I can test it by just renaming /opt/kf5.  (Another good reason 
for building in /opt).


  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] dependencies for LXQt

[Pierre Labastie]

On 04/03/2016 17:16, Ken Moffat wrote:

On Fri, Mar 04, 2016 at 12:10:46PM -0300, Fernando de Oliveira wrote:

Em 04-03-2016 09:08, Pierre Labastie escreveu:

(trimming severely)

On 04/03/2016 11:36, Fernando de Oliveira wrote:

Em 04-03-2016 06:15, Pierre Labastie escreveu:

Does somebody know which kf5 and
plasma deps are really needed?

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.

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.


The last time I built lxqt, the only KF5 deps it needed were:

extra-cmake-modules

kwindowsystem (I built those two before liblxqt)

kguiaddons (I built that before libstatgrab)

I can see that I also built oxygen-icons from kde4, and the qt5
version of polkit-qt.

 From what I remember, it really required openbox (I had thought
other 'box WMs might pass muster).

ĸen

Thanks,

Actually, as I said, I built all of kf5 and plasma. I found a small (but 
annoying, because libksysguard was not applied the fix) bug in the 
plasma instructions, (see commit r17061), so hopefully, making the book 
better.


Otherwise, the LXQT build went smoothly, so I think the instructions are 
good. I have built openbox, lxdm and sddm. I still have to test that now.


To Fernando, I understood you hadn't understood my first post. That's 
why I explained. I'm glad we agree (I do not like LXQt either, for the 
same reasons as you...).


Regards
Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] dependencies for LXQt

[Ken Moffat]

On Fri, Mar 04, 2016 at 12:10:46PM -0300, Fernando de Oliveira wrote:
> Em 04-03-2016 09:08, Pierre Labastie escreveu:

(trimming severely)
> > On 04/03/2016 11:36, Fernando de Oliveira wrote:
> >> Em 04-03-2016 06:15, Pierre Labastie escreveu:

> >>
> >>> Does somebody know which kf5 and
> >>> plasma deps are really needed?
> > 
> > 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.
> 
> 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.
> 
The last time I built lxqt, the only KF5 deps it needed were:

extra-cmake-modules

kwindowsystem (I built those two before liblxqt)

kguiaddons (I built that before libstatgrab)

I can see that I also built oxygen-icons from kde4, and the qt5
version of polkit-qt.

From what I remember, it really required openbox (I had thought
other 'box WMs might pass muster).

ĸen
-- 
This email was written using 100% recycled letters.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] dependencies for LXQt

[Fernando de Oliveira]

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

Re: [blfs-dev] dependencies for LXQt

[Thierry Nuttens]

2016-03-04 13:08 GMT+01:00 Pierre Labastie :
> 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.
>
> Regards,
> Pierre

If you are interested, I have all the ports build for lxqt with the
needed library

https://github.com/NuTyX/lxqt
lxqt and lxqt-extra ( lxqt applications)
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] dependencies for LXQt

[Pierre Labastie]

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.


Regards,
Pierre

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] dependencies for LXQt

[Fernando de Oliveira]

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?

-- 
[]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

[blfs-dev] dependencies for LXQt

[Pierre Labastie]

Hi,

I am struggling through the dependency chain for LXQt, and I end up 
needing all the dependencies for KDE-frameworks and plasma. 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. So it is 
hard to know what deps are needed (I may have missed something in the 
book), and building LXQt is therefore very heavy (far from the 
"lightweight" desktop advertised). Does somebody know which kf5 and 
plasma deps are really needed?


Regards
Pierre

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page