KDE 4 SVN package repositories (i686/x86_64, release/debug)

gothicknight · 2008-06-02 15:14:40

OK, I've installed the packages and some issues were solved by conflics with tardo repo qt package.

The packages are great (thanks!) but the overall quality is still far fetching. KDE 4.1 is by all means still a beta and more love is needed. Dolphin crashed a few times and taskbar options are still lacking way too much options

All in all, the packages are great, the KDE itself still needs maturity. With help reporting/documenting/fixing bugs it'll get there

tanis · 2008-06-02 20:49:00

I modified extragear-network4, so it includes ktorrent.
There is also new extragear-libs4 package, that includes kipi plugins needed by digikam, and updated extragear-graphics4 package, with digikam this time

If [testing] repository is added, digikam complains about missing libexiv2.so.0 library: "ln -s libexiv2.so.2 libexiv2.so.0" inside /usr/lib should do the trick.
However, I have no idea if it affects digikam in any way. It starts, but it's possible that weird things may happen
(in addition to "normal" weird things that may happen because this is svn version of digikam )

Again, extragear-* packages (Except for extragear-plasma4) were not part of KDE 4.1 Beta, and are built from KDE's svn - they could be even less stable than Beta1 ones.

All extragear-* packages are now in both x86_64 and i686 repositories

ozar · 2008-06-03 04:13:46

tanis, is there any chance of getting koffice2 and k3b into the mix?

Those two would pretty much complete my system, I think. I thought maybe k3b would be in extragear-multimedia4 but apparently not.

Thanks again for your hard work on this.

tanis · 2008-06-03 04:57:21

k3b is in extragear-multimedia4. Unfortunately I couldn't compile it, and it looks like problem with Qt 4.4.0. I would probably have to start
using qt-copy, which leads to even more problems - so I decided to disable k3b completely.
Trying to get things that were not part of Beta1 working with other packages from Beta1 is more challenging, and I don't think it's worth the extra work.
I'm rather thinking about another repo with svn-based packages (since extragear-* and koffice2 would be from svn anyway),
with qt-copy and newest sources available in svn. Not updated daily, like Mark's, but "from time to time"

ozar · 2008-06-03 15:25:24

Okay, thanks, tanis!

I'm using command line for burning until we can get a working k3b.

Yeah, if you go with a separate repo that includes all the extras, I'll certainly be giving it a spin.

Thanks again.

tanis · 2008-06-04 22:01:16

I have added another repository. Packages are built from SVN sources. Release number is (similar to Mark's packages) a date when SVN was updated.

So far only x86_64 packages are present:

[tanis-kde4-svn]
Server = http://csclub.uwaterloo.ca/~jkschmid/arch/kde4-svn/x86_64

Those packages need qt>=4.4.0. The repository includes qt-copy, built from KDE's svn version
of Qt, but dependencies don't force it. So either qt from Arch's official repository, or qt-copy
can be used. I am using qt-copy, and I have no idea if using official qt package doesn't break something.
In case it doesn't, and someone wants to stick to official qt version - it's possible.

The whole thing (except for qt-copy, and some other small dependencies) goes into /opt/kde4-svn/.
If anybody used my kde4 repository, he should update his .bashrc file to run /etc/profile.d/kde4-svn.sh instead
of kde4.sh.

Not all the things are there, some of them didn't build, some of them had some dependency problems.
I will rebuild them with newer sources, and upload newest version of every package to the repository.
Dependencies also should improve over time. I don't plan to do that daily, just "from time to time"
Oh, and I need to run the whole thing for i686 too. I'll write when it's done.

Packages in the repository include Amarok2 (though it didn't want to play music in my case, so something is wrong with it ),
k3b, koffice and some other goodies

Also, if anybody is interested in building it by himself, here is the pack with all the scripts used:
http://csclub.uwaterloo.ca/~jkschmid/ar … ts.tar.bz2

Just download it, unpack it and run: ./get_all_svn ; ./build_all (actually two packages should be built and installed manually before that)
After that, ./update_all_svn updates SVN, and ./build_all builds all packages for which revision number changed.
There are also some other handy scripts. If anyone is interested, I can explain how it works

Oh, some of the packages might not make much sense, they were generated semi-automatically. Over the time scripts should improve too

ozar · 2008-06-05 01:18:10

tanis, thanks for the new repo(s).

Just wondering... are you doing anything to make your gtk apps such as firefox look better under kde4, or are you using any gtk apps "as is"?

I've been using the qtcurve kde4/gtk2 packages along with gtk-chtheme option as described in the wiki:

http://wiki.archlinux.org/index.php/Uni … d_GTK_apps

...and it looks pretty good, but the following option looks like it might be easier and very worthwhile, too:

http://www.kde-apps.org/content/show.ph … tent=74689

Have you tried it by any chance?

tanis · 2008-06-05 06:21:02

ozar: I haven't tried that yet. The first solution should work without adding any packages to the repo, right?
Have you tried both? Do you think the second one is better and it's worth adding it to the repo?

By the way - the script pack (http://csclub.uwaterloo.ca/~jkschmid/ar … ts.tar.bz2) has been updated,
it should be sufficient to just run (for the first time, and every time after that):
./update_all_svn && ./build_all

ozar · 2008-06-05 13:03:10

tanis wrote:

ozar: I haven't tried that yet. The first solution should work without adding any packages to the repo, right?
Have you tried both? Do you think the second one is better and it's worth adding it to the repo?

Yes, the first solution works using the packages that are already in the community repo. I've not tried the second solution, but I think that's what they are using in KDEmod4. It appears to fix the Gtk ugliness without changing the default kde4 theme. The KDEmod4 guys probably have a pkgbuild for it, but I'm not sure if they've released any pkgbuilds, or if it would work with your packages.

pressh · 2008-06-05 13:44:08

ozar wrote:

but the following option looks like it might be easier and very worthwhile, too:
http://www.kde-apps.org/content/show.ph … tent=74689
Have you tried it by any chance?

it only allows you to change your gtk theme (which you can also do with gtk-chtheme and the like). There is no way with that package to make your gtk apps look like your qt apps, except with the gtk theme they have in their download section (you can just extract it and copy it in your ~/.themes folder.

If you want your gtk apps take the look of any qt4 theme you chose you should take a look at gtk-qt-engine, though it is highly unstable at the moment so not really useful till they fix the instability.

ozar · 2008-06-05 15:28:39

pressh wrote:

If you want your gtk apps take the look of any qt4 theme you chose you should take a look at gtk-qt-engine, though it is highly unstable at the moment so not really useful till they fix the instability.

I've always found the gtk-qt-engine to be overly buggy, and it feels like it slows down my browser for some reason, but I don't get all that with the qtcurve/gtk-chtheme fixes. The Gtk ugliness thing is by far my biggest complaint about KDE. I've also tried repeatedly to use Konqueror as my default web browser, but it's got problems of its own, and I can't stick with it for more than a day, or two.

Hopefully, something really good will happen in the future to fix all this.

Last edited by ozar (2008-06-05 15:29:15)

tanis · 2008-06-05 20:45:50

I have created i686 repository as well:

[tanis-kde4-svn]
Server = http://csclub.uwaterloo.ca/~jkschmid/arch/kde4-svn/i686

Also, there are some updates to x86_64.

Script package has been updated as well. Also, if any one started using it, graphicsmagick dependency is no longer required (koffice doesn't compile if it's installed)
and should be removed manually if it was added by the script (it won't be added again, unless koffice starts building properly)

UPDATE: Now i686 contains even more packages than x86_64

UPDATE: Added KOffice for i686 (was missing before).

Last edited by tanis (2008-06-06 01:09:38)

TripleE · 2008-06-05 23:32:34

awesome. I am downloading the i686 version now.

tanis · 2008-06-06 01:11:44

Since the list of packages changes, to get all the packages, including those new in the repository, run:
pacman -Sy --needed kde4-svn-all - this will install packages not installed before and update those with newer versions in the repository, without reinstalling those that were not updated
Running pacman -Sc after that is probably a good idea to get rid of old packages.

ozar · 2008-06-07 19:42:40

Does anyone know if there there a listing anywhere that describes what apps are in all the different packages, such as what's in each of the extragear and playground packages, for instance?

I looked around for a bit on the KDE site but couldn't find a detailed packages description anywhere.

n8schicht · 2008-06-07 19:56:23

Awsome new svn-repo, thanks a lot of times!
Is anyone able to load a superkaramba applet in plasma? I couldn't make it display any. Or is this a bug?

ozar · 2008-06-10 00:30:30

Hi, tanis!

I just installed your svn packages (typing from it now) on a fresh Arch installation, and they seem to be working pretty well. I'm seeing lots of icons that have been missing from other builds, as well.

Two packages that I was worried about were koffice2 and k3b. Both are starting up fine, but I've not had a chance to really use either of them to see how well they work. Note that k3b wouldn't start at all until after I installed the libsamplerate package. It appears to be a missing dependency, or it didn't get picked up when I installed the svn packages.

Does anyone happen to know why kmix starts up on each and every login, and better yet, how to stop it from doing that? I've tried the various options in the kmix settings, but it still starts up each time.

Last edited by ozar (2008-06-10 00:31:06)

anykey · 2008-06-10 09:17:32

you might check whether kmix ended up being symlinked into .kde/Autostart.

Just a guess though.

stonedz · 2008-06-10 13:20:05

Thank you tanis for the packages, they're working very good on my PC (i686 repo). A trivial question, I've updated to the latest packages but in the About Kde section the version number is still the same (Using KDE 4. 0.81 >=20080527), I guess that's normal but I wanted to ask if I'm right.

Thank you again,cheers!

Barghest · 2008-06-10 18:44:25

Hi,

there is something unclear for me. If I read correctly this KDE4.1 beta goes in /opt.

What I want to know now I, what happens, when KDE4.1 is finally released and comes into an official repo? Will there be any issues because of the structure or will pacman just update without complaining?

Furthermore I'd like to know if I I have something to do if I already have some KDE programms installed (kile, k3b)?

Thanks

tanis · 2008-06-10 18:59:24

@stonedz: Those version number don't change with every SVN commit, so they don't necessary must reflect the date it was pulled from SVN

@barghest: This has nothing to do with official repositories. AFAIK KDE4 will go into /usr, once it is part of official Arch repo. There is already highly experimental repository with some preliminary KDE4 packages, that go into /usr. The transition will probably the same as with qt3 -> qt4: 'qt' was renamed to 'qt3', and 'qt4' was renamed to 'qt'. Some things broke, but now 'qt' means 'Qt4' everywhere. So, at some point all KDE 3.5 packages will be renamed to kdebase3, kdelibs3, etc, and there will be some new packages called simply 'kdebase', 'kdelibs', containing KDE4. I might be wrong, but this is how those experimental packages look like: http://git.archlinux.de/cgit.cgi?url=kde-testing. But this is large change, and a lot of things might break. On the other hand, my repository (actually both of them, Beta1 and SVN) lets you see how the KDE4 looks like, and even use it, but without doing any changes to your existing installation. Beta1 and SVN packages goe into /opt/, and shouldn't break existing KDE3.5 installation (as long as you have separate user for KDE4). But this is not a part of official "road to KDE4". So when KDE4 appears officially in Arch, you should remove my packages, and install KDE4 from official repository instead. Existing configuration of KDE4 programs should work fine, although it might be necessary to change the directory name (~/.kde4-svn -> ~/.kde, or something else, depending on what Arch Devs decide it to be).

Barghest · 2008-06-10 19:06:08

Thanks tanis for your explanation.

I think I will be patient until an official version is released and take a first glance via a Live CD.

ozar · 2008-06-10 19:56:06

Hi, tanis...

Just wondering if you plan to do the KDE4.1-beta2 packages when they are released?

If I'm not mistaken, that will be on June 24th.

Thanks for your work on the current beta1 and svn packages.

Last edited by ozar (2008-06-10 20:01:18)

tanis · 2008-06-10 21:12:29

@ozar: I do According to http://techbase.kde.org/index.php?title … e_Schedule it should be in 2 weeks

Cipher · 2008-06-14 01:10:46

can you updated your svn-packages please. i have no time to build from svn myself

Arch Linux

#26 2008-06-02 15:14:40

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#27 2008-06-02 20:49:00

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#28 2008-06-03 04:13:46

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#29 2008-06-03 04:57:21

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#30 2008-06-03 15:25:24

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#31 2008-06-04 22:01:16

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#32 2008-06-05 01:18:10

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#33 2008-06-05 06:21:02

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#34 2008-06-05 13:03:10

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#35 2008-06-05 13:44:08

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#36 2008-06-05 15:28:39

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#37 2008-06-05 20:45:50

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#38 2008-06-05 23:32:34

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#39 2008-06-06 01:11:44

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#40 2008-06-07 19:42:40

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#41 2008-06-07 19:56:23

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#42 2008-06-10 00:30:30

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#43 2008-06-10 09:17:32

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#44 2008-06-10 13:20:05

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#45 2008-06-10 18:44:25

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#46 2008-06-10 18:59:24

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#47 2008-06-10 19:06:08

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#48 2008-06-10 19:56:06

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#49 2008-06-10 21:12:29

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

#50 2008-06-14 01:10:46

Re: KDE 4 SVN package repositories (i686/x86_64, release/debug)

Board footer