On Mon, Aug 17, 2015 at 9:56 AM, Ken Moffat <[email protected]> wrote: > On Mon, Aug 17, 2015 at 12:08:25AM -0500, Bruce Dubbs wrote: >> Ken Moffat wrote: >> >On Sun, Aug 16, 2015 at 08:06:25PM -0500, Bruce Dubbs wrote: >> >>Bruce Dubbs wrote: >> >> >> >>If we do, we may also be able to get in KDE Applications 15.08 which are >> >>scheduled right now for Aug 19th. Plasma 5.4 is also due on Aug 20. >> >> >> >>On the other hand, if we wait for the latest on everything, we will end up >> >>waiting forever. >> >> >> >>To freeze or not to freeze, that is the question. >> >> >> >> -- Bruce >> >> >> >My current view is that BLFS (on LFS as of a few days ago) is not >> >ready for release. For me, qt-5.5.0 appears to not work adequately >> >if built in /usr, and appears to be very fragile when trying to >> >build it (see my post from a few minutes ago). Also, sddm did not >> >work reliably (poweroff, reboot, suspend) when I last tested it, i.e. >> >it seems to need more daemons but we haven't worked out which. To >> >reiterate on that - I was unable to use startkde (i.e. plasma) with >> >kde5 in /opt because there was nowhere to tell sddm how to find >> >plasma. If I ran startkde from runlevel 3 I could, after stopping >> >that, telinit 5 and get all of sddm working - until I rebooted, at >> >which time I lost poweroff, reboot, suspend. >> > >> >But last time I looked, the main book did not have plasma, so why >> >do you care about a point increase of that ? >> >> I was hoping to add it. >> > That would be nice - from the instructions in the systemd book I was > able to work out which packages I could probably drop (in the end I > needed one of them) - anything to do with bluetooth and mobile > conenctivity is a target for not being useful on a wired desktop, > > I was surprised tht Wayland is not the throw-out-Xorg package I had > assumed, it seems to be treated as a new interface to X. But it is > required for plasma (and Mesa needs to be built against it, with the > driver selected). > > (And the same with kf5 itself - by looking in the details of the > systemd book I could see what looked unnecessary. At that time I > did not see anything which used kapidox, and two of the runtime > deps, Jinja and PyYAML - both python modules - do not seem to be in > the book.)
They are in the systemd book, but you are correct, they are not in the sysvinit book. > >> BTW, Qt5 has been working fine for me using KDE Apps like kdenlive. I do >> run them in xfce though. And I don't like display managers, but I'll start >> working on them after the freeze. >> >> -- Bruce > > For qt5, it has been working fine for me since 19th July on this > system (the one which is hosting qemu). But that is in /opt/kf5. > I had hoped to treat it as my main version of qt (only vlc needs qt4 > in my normal build), so I wanted to put it in /usr. > > The systemd book has/had instructions for qt-5.4.2 in /usr, with > qtchooser. My attempts to use qt-5.5 in /usr, either with or > without qtchooser, have all failed (either qupzilla does not link, > or one of the kf5 packages used by lxqt does not build). At the > moment I'm revising my scripts to use /opt/qt5 again. > One of my plans is to completely overhaul the qt pages in the systemd book before the next release. I barely know anything about Qt though, so it will be a time of troubleshooting for those packages. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
