Armin K. wrote:
Hi everyone,
Not so long ago, I've notified the list of my KDE Frameworks work and
received some feedback along it.
The main question back then was "Can all of the Frameworks Packages be
installed at once like for example Xorg Libraries?"
Well, I've managed to get the instructions for that ready for testing so
the answer is "Yes, they can be!"
However, I have decided to keep all the standalone packages in the book
mainly because there will be some apps/packages that won't require most
of the (biggest and longest to build) packages from that section.
Which packages currently use KDE Frameworks or portions? I do imagine
that we will eventually add it to BLFS, but need to weigh the benefits
vs the support burden.
Building all of the Frameworks at once is only useful if building the
entire Plasma desktop.
When it comes to maintenance, I've implemented a LFS like packages.ent
named kde5/kde5.ent. It contains shared XML headers for Frameworks and
Plasma packages (download, md5, size, build size, sbu, etc) so they are
shared between the standalone packages and all-at-once instructions.
Frameworks are released monthly and I have yet to see them changing much
besides translations and some minor fixes, so the maintenance burden of
the individual page should be minimal.
So far, my work can be found here:
http://www.linuxfromscratch.org/~krejzi/kde5/kde5/frameworks.html
or use the direct link to the new page:
http://www.linuxfromscratch.org/~krejzi/kde5/kde5/kf5.html
Any feedback is welcome.
Having both the full Frameworks and the individual packages seems like a
lot to add. I lean toward the consolidated page with perhaps some
generic instructions for the individual packages like:
http://www.linuxfromscratch.org/blfs/view/stable/kde/add-pkgs.html
I believe that I've done everything I can to get the Frameworks section
polished as it can be. With this done, I believe they are ready for
inclusion in our books - but I'll leave that to the book editors.
I can help integrate it but for the main branch they would need
additional testing, mainly because systemd branch has way different Qt
instructions which I also use, and the Frameworks have been written with
such instructions in mind.
There are few packages outside of Frameworks section that need to be
added, mainly for the kapidox framework. There's one library - yaml and
4 Python modules - setuptools, markupsafe, jinja2 and pyyaml. All of the
packages are available in the systemd branch and contain no branch
specific instructions so they can be copied just fine.
As for the KDE Plasma Desktop, I have yet to build latest version and
update the instructions, but I still don't think it will be good enough
for production use mainly because there are no apps at the moment (KDE 4
apps can be used though just fine) and some of the desktop functionality
is missing - in fact everything that depends on the PIM suite.
This may be the key for adding to trunk. KDE4 took a while to mature
and this may be the same.
I like to think of BLFS as leading edge, but not bleeding edge. This
looks a little early for BLFS, but there is a huge amount of work here
and I appreciate it.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
