Hello,
I have searched the internet and KDE sites on packaging KDE and am unable to find details on how to properly do this.
I have been able to successfully able to build KDE SC 4.10 on RedHat Enterprise 6.4 with some updated dependencies off of fedora 14 - 17 that have been re-based using smock/mock/rpmbuild into RHEL el6 rpm's that properly integrate into RHEL as well.

I have 99% of the components built and am only running into four minor issues now as well as packaging.
The first is I cannot utilize the libbluedevil / bluedevil bluetooth libraries. Each time the system starts up, or you access the bluetooth controls inside KDE, that component crashes. So I re-build without it and it is fine.

The second is I am unable to use the NetworkManager tray icon / NetworkManager system as the word Interface is written in the panel overriding the items. So I am utilizing wicd instead and it works fine. I can always exclude the NetworkManager component from the kdesrc-build

The third is kmixer. It works just fine until you logoff, then it crashes, but I need this for volume management.

The fourth is Nepomuk. It compiles, but I get the message "The Nepomuk Installation is not complete. No desktop search settings can be provided". I am now trying to upgrade virtuoso from 6.1.2 to 6.1.6 via smock and re-compiling to see if that helps.

After all of this, I believe it is still in a good state to package as there are a few people who want this, and although it is not ready for prime-time, nor am I ready to support a packaging for a large group of people, I would like to know how.

Right now, I am using kdesrc-build and building kde into /opt/kde4 and qt into /opt/qt4. Then setting KDELIB/KDELIBS, etc.. as well as a new KDEHOME as not to interfere with my old KDE home directory.

Can anyone point me to a resource that I can use to package this? I know the CMakeList.txt files support CPack but that is not configured.

Thank you.

did you see http://blog.welmers.net/bastiaan/2013/0 ... n-el6.html & viewtopic.php?f=63&t=101840&p=247439&hilit=redhat#p247439

Yes,
and I actually replied to the blog way back on Feb 2nd and it has been awating moderation since. This is when I tried the 4.9.5 version that was built and I had not set my KDEHOME and it upgraded my current home and would not work properly as the problems he described about the crashes at each close and the profile re-setting itself I had as well with 4.9.5, but he could not get kdesrc-build to work properly only a couple things there worked, so he build the rest via source. There was no going back to the old KDE at that point, so I switched to GNOME as I started my venture in building from source as well.

I took some of his ideas and that is where I knew to link the libraries properly and set the display manager properly, but I found all appropriate dependencies to get the whole thing to build with kdesrc-build with branch 4.10 instead of 4.9.5 and other branches where necessary. Perhaps it was just changes in 3.9.5 to 4.10 / 4.10.1 which made it able to do so. I don't have the profile issue that was occurring as he did, my profile stays fine, it is just those other couple quirks which I can live with for now and perhaps work out later with proper library dependencies.

Granted, I could just tar.gz the /opt/kde4 and /opt/qt4 directories like he did, but I wanted to be able to spec out the dependencies to ensure a clean install. kdesrc-build checks for all the dependencies via the CMakeList.txt files, so I was hoping there was a way to piggyback that, perhaps with CPACK entries.

To the best of my knowledge, most KDE Packager teams tend to stay away from CPack as it produces "low quality packages".
I would advise looking at the *.spec files carried by Fedora for the version of KDE shipped with RHEL 6.4 to get an idea on where to start.

The Fedora KDE team may also be able to help you, if you ask on their mailing list.