On Wednesday 01 April 2009 23:24:58 hajma wrote:
> I'd like to start working on KDE4.2.2 since 4.1.4 has it's limitations and
> is basically obsolete by now. I started to abuse the kde-4.2 subdirectory
> for that. (Yes, branches are too complex)
That's fine. I hope you find that the patches from KDE 4.1.4 still apply
pretty well to the 4.2.2 tarballs. I *think* I went over them all and pushed
what made sense into KDE SVN before KDE 4.2.0 came out; we do have a few
patches that are too solaris-specific to push in well.
Pursuant to the whole branches / repos discussion I think this (using a
subdirectory) is fine for now; are you starting pkgtool by hand for those
builds?
> I've pushed the initial 4.5.0 FOSSqt.spec. It is very ugly and it is still
> having issues with one unixodbc header (might make sense to try with
> unixodbc 2.2.14) (but if configured without sql support, at least make
> passes fine). It only required one delinuxation patch so far, and I've
> reported the issue to trolltech.
That's quite remarkable. Er, ... where did you push it to? Please put it in
kde-4.2 as well for now and don't overwrite the existing qt 4.4.1. The reason
for doing that is that we have a relatively stable KDE 4.1.4 setup, and we'd
want to preserve that somehow (e.g. repo copy or named tag) while working on
KDE 4.2.2.
> On a related note I am not sure about the cvsdude thing, I believe we
> should make the FOSS* packages more spec oriented and straightforward, with
> real patches etc. Also the patches should be pushed upstream, instead of
> accumulating them in a cvs, it's a nightmare when increasing version. It is
> certainly very cumbersome ATM and IMO complicates their "outsourcing" to
> sourcejuicer or whatever. WDYT?
There are a couple of other discussions going on about that. They are only
partly orthogonal:
- where to develop patches
- where to use the patches for specfiles
- which repo(s) to use
--
Adriaan de Groot - KDE Quality Team, KDE-Solaris
- http://www.englishbreakfastnetwork.org/
- http://solaris.kde.org/
