Douglas R. Reno wrote:
On Fri, Mar 25, 2016 at 2:40 PM, Bruce Dubbs <[email protected]> wrote:

I've been trying to get the kf5 apps in the book to be about the same as
we had for kde4.  I've been able to do this with the exception of kdepim.

In the latest release of kf5 apps, there are 187 tarballs.  This includes
a mix of a few kde4 packages, but mostly kde5 packages.

I'm having trouble figuring out dependencies for libkdepim.  The lastest
I've found is kdepimlibs needs akonadi, but the akonadi-15.12.3.tar.xz
package only appears to provide KF5AkonadiServer.  Looking at Arch, the
dependency tree looks like:

libkdepim needs
   kdepim-runtime needs
     akonadi-calendar needs
       akonadi-contact needs
         akonadi-client needs
           akonadi

The problem is that there is no released version of akonadi-client
although there is a git repo for it.

Overall the ultimate purpose is to provide apps.  kdepim provides:

akregator       Feed Reader
blogilo         Blogging Client
kaddressbook    Contact Manager
kalarm          Personal Alarm Scheduler
kleopatra       Certificate Manager and Unified Crypto GUI
kmail           Mail Client
knotes          Popup Notes
konsolekalendar Command line tool for accessing calendar files
kontact         Personal Information Manager
korganizer      Calendar and Scheduling Program
ktnef           Viewer/extractor for TNEF files

I have never used any of these.  Is it worthwhile to pursue adding them to
the book?

   -- Bruce

I personally think that it is still worthwhile to pursue adding them to
the book. As a matter of fact, I am now in the process of upgrading my
Toshiba with my old KDE4 files on it to the latest -dev version of LFS and
-BLFS with the last KDE4 release that we supported, and upgrading the files
to the KDE5 equivalents. I have used KAlarm, Knotes, Korganizer,
Kaddressbook, Kontact, Akgregator, and Bloglio for somewhere around 6-8
years now, as it contains all of my journals and contacts in it. I also
have some old Kopete conversations that I would like to save. At first, I
thought that the idea of a fresh jhalfs build would work. However, this
system is so old now (in build age, and in physical age) that I actually
think that it would be faster to just upgrade everything in-place, although
I realize I am at my own risk here.

I suppose that we should ask people on -support as well.

My hope is that my conversion of files goes without issue!

When I get around to looking at the KDEPIM-5 stuff, I can report back if
you would like. I can also make an akonadi-client tarball if needed, as I
already have most of the infrastructure setup on my workstation from when I
used to work on KDE -dev stuff.

kdepim5 is very complicated.  Take a look at:

https://github.com/elkrejzi/system-management/blob/master/buildscripts/buildkdepim-frameworks#L12

I want to get caught up with outstanding tickets and then look at both kdepim5 and dolphin.

  -- Bruce

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

Reply via email to