Added by devnet, last edited by devnet on May 21, 2008  (view change) show comment

Labels:

environment environment Delete
development development Delete
foresight foresight Delete
359 359 Delete
kde kde Delete
historical historical Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

What's this About?

This page will be a punch list/general info page of sorts for getting KDE 3.5.9 up to stable and installable on Foresight Linux.  Until KDE 4.1 is released sometime in late July of 2008, 3.5.9 will provide the best experience for users.  Realizing this fact, I'd like to assemble a team of packagers to bring KDE from 3.5.7 version found on the project page to the most recent 3.5.9 release. 

NOTE

This will be a separate initiative than KDE on Foresight 2.  This will be a standalone system.  The goal is to provide a platform that is stable.  Once accomplished, we can work out the kinks it takes to install KDE4, XFCE 4.X, and Gnome 2.X on the system (though it should already be fairly easy...some things will give problems like pulseaudio, etc).

Status

Currently, we are devoting all our development time to working on getting 3.5.9 Stable to Foresight. We have released no builds as of yet but should have a build for developers (pre-alpha) ready in the first week or two of May. Look for a build then...remember though, it will be our first build and will have many things that do not work! (but many that do as well )

Getting Started

Development Environment Setup 

When setting up my conary development environment, I am sure to organize it well.  For example, I create my conary working directory inside /home/user.  From there, I create labels for each project I work on.

[ddevine@dhcp160 conary]$ ls -l
total 20
drwxrwxr-x 6 ddevine ddevine 4096 2008-04-09 16:05 builds
drwxrwxr-x 7 ddevine ddevine 4096 2008-04-09 16:04 cache
drwxr-xr-x 3 ddevine ddevine 4096 2008-03-31 15:50 caffeine.rpath.org
drwxrwxr-x 4 ddevine ddevine 4096 2008-04-08 15:07 foresight.rpath.org
drwxrwxr-x 3 ddevine ddevine 4096 2008-04-10 16:36 kde.rpath.org

 As you can see above, I have a directory for each project lable I work on.  I've created kde.rpath.org for this project.  Inside each project label directory would be the namespace and tag (for explanation of the entire conary version string, look here) that I will be working with.  Inside foresight.rpath.org above, I work with many different branches including fl:2-devel and fl:devel.  Inside the kde.rpath.org directory, we'll be working with fl:2-devel so create that directory.

Context inside ~/.conaryrc for building for KDE 3.5.9 Edition of Foresight Linux should be as follows.  I've chosen kdesight2 as my context but you may substitute anything inside. 

[kdesight2]
buildLabel                kde.rpath.org@fl:2-devel
contact                    kde@lists.rpath.org
installLabelPath         kde.rpath.org@fl:2-devel foresight.rpath.org@fl:2-devel conary.rpath.com@rpl:2-qa

After you context is set inside .conaryrc, go into the working directory and set context:

cd ~/conary/kde.rpath.org/fl:2-devel
cvc context kdesight2

Replace kdesight2 with whatever your context name is.

 More information will follow.

PUNCHLIST TASKS 

    • If it is possible, create an entire theme.tar.gz for use in a trove for Foresight
    • Customize/Create diffs for base KDE rebranding (Konq homepage, etc)
    • Package up individual customizations into troves
      • Create group-foresight-kde-branding or something similar to contain all the customizations
        • Add to required groups before releasing
    • Pick default icon theme - currently Crystal SVG (too blue?)
  • Look into running pulseaudio in daemon mode to fix problem of it not executing** Check how Fedora gets theirs to run by default (they run a script in /usr/share/env)
    • What else is in that kde-settings trove?
  • Deployment
    • Promote troves to foresight label
    • Build groups
    • promote to 2-qa
    • Build alpha1 images (Target May 1, 2008)