KDE 3.5.10 repository

lucke · 2008-08-28 07:57:00

It works okay now, tanis. One thing I've noticed: KDEmod3 calls those files kdelegacy, so there's apparently some trick to it. My headache prohibits me from digging any deeper, at least for now :-)

lucke · 2008-08-28 08:03:38

MONODA: daemon is called kdm3.

3lusive · 2008-08-28 15:42:04

THANK YOU for doing this.

I'm currently using my Linux laptop for a work contract, I do have 3.59 and 4.1 installed but
didn't like kde4.... I need 3.59 and use it everyday for apps for work, I still need it.

Anyone who reads this, i'm thinking of becoming a desktop aGNOstiC..... and eventually i'm going
to configure my system to load COMPIZ and then a panel like AWN and nothing else.

NO DESKTOP is the way to go, for those of us smart enough to do it, I have been pro-KDE all the way
but i'm using 50/50 gtk/kde apps.....

I loooooooooooooove Compiz. Big Compiz fan. KWin DOES NOT WORK with i965 Intel graphics.

KDE4 "Desktop" NO kde 3.5.9 apps = yes, kde 4.x apps = yes, but PLEASE NO DESKTOP.....

hopefully more people will become desktop AGNOSTIC and just run something cool like AWN+Compiz.

check out http://www.3lusive.com blog for my AWN movie.

-jim

tanis · 2008-08-28 16:56:58

@MONODA: As lucke wrote, it's 'kdm' not 'kdm3'.
As for knetworkmanager its dependencies are not updated, but it's still KDE3 package.
The same goes for example for katapult.
You may either install them ignoring dependencies, or pull kdelibs 4, and phonon and few other packages.
They don't interfere with the rest of KDE3. I could create special versions of those packages with updated dependencies,
but there could be way more of them in AUR - it's better to ask their maintainers to update those dependencies so they would use 'kdelibs3' instead of 'kdelibs'.

As for the menu problems - I have no idea, I haven't experienced anything like that In my 'lost and found' there are only some Arch related entries.

Last edited by tanis (2008-08-28 16:59:19)

tanis · 2008-08-28 16:59:26

@lucke: I will have a look at those pam files at some point. If you find a solution, please share
Also, is it possible to have both kdemod (3.5) and kde 4.1 from [extra] installed and be able to run kdemod
without kde4's plasma starting at the same time? Do you know how?

lucke · 2008-08-28 17:04:25

From KDEmod's forum:

KDEmod 3.5.9 does now conflict with KDE 4.1, so there is no side-by-side installation possible anymore

Last edited by lucke (2008-08-28 17:04:43)

tanis · 2008-08-28 17:07:05

@lucke: So I guess they have the same problem

ozar · 2008-08-28 17:42:42

I've given up on KDE4 until at least 4.2 is released but might give 3.5.10 a try.

Thanks for the repos, tanis!

funkyou · 2008-08-29 04:27:32

lucke wrote:

From KDEmod's forum:
KDEmod 3.5.9 does now conflict with KDE 4.1, so there is no side-by-side installation possible anymore

Not true anymore A side-by-side installation is possible again, at least on i686 (x86_64 still needs a rebuild, so we didnt change the forum post for now)... Well, making it work was one of the best packaging adventures we ever had

tanis wrote:

When I was modifying kde-common, I changed kde and kde-np files from /etc/pam.d to kde3 and kde3-np. I guess it doesn't work for some reason. I changed those names back. Now, however, it might conflict with kdm from KDE4...

Rename the pam files, then use this in the configure line of kdebase: --with-pam=NAME_OF_YOUR_PAM_CONFIG_FILE
(e.g. --with-pam=kdelegacy, if the config is called kdelegacy)

tanis wrote:

I don't think modular KDE is a good idea and having a choice is

Well, modular KDE = choice
And as we are some smart people who like to push things forward, we also included the possibility to install complete KDE modules, just like when you are installing non-split packages

tanis · 2008-08-29 17:22:17

funkyou wrote:

Not true anymore A side-by-side installation is possible again, at least on i686 (x86_64 still needs a rebuild, so we didnt change the forum post for now)... Well, making it work was one of the best packaging adventures we ever had

Would you share how did you do that?
And thanks for the PAM info

lucke · 2008-08-31 17:26:00

libopensync (needed by kdepim3) is missing in the repos. I've found it here. Maybe it'd be a good idea to put that package in the kde3 repo?

tanis · 2008-08-31 17:33:38

There are some packages removed due to KDE3->4 cleanup. Those are:
libopensync showimg libkexif gnash-kde klogic knetload schafkopf kiosktool kradio metatheme mozillaqs kkbswitch knetworkmanager.
I will try to add them to kde3 when I find PKGBUILDs for them (anybody knows where to find them? )...

Last edited by tanis (2008-08-31 17:44:54)

lucke · 2008-08-31 17:51:30

There's libopensync-unstable in AUR, maybe you can use its PKGBUiLD?

That one package is a bit different than the others, because it's a dependency for a base KDE3 package. Can't install KDE3 after a clean install without it.

attila · 2008-08-31 17:59:41

tanis wrote:

I will try to add them to kde3 when I find PKGBUILDs for them (anybody knows where to find them? )...

I make a backup of this sources from my abs tree before cron do a sync. So you can have them if you tell me how i can attach the archiv of it here (or wherever you wants them).

tanis · 2008-08-31 18:06:32

You can send a normal email to: sjakub at gmail dot com.

attila · 2008-09-01 09:09:20

tanis wrote:

You can send a normal email

You should have it, if not say it.

funkyou · 2008-09-01 20:43:09

tanis wrote:

funkyou wrote:
Not true anymore A side-by-side installation is possible again, at least on i686 (x86_64 still needs a rebuild, so we didnt change the forum post for now)... Well, making it work was one of the best packaging adventures we ever had
Would you share how did you do that?

If i remember correctly...

1. Add this and this patch to kdelibs
2. Add this patch to kdebase. Be sure to source the KDE profile files directly in startkde and not systemwide = make then non-executable in /etc/profile.d

If i didnt forgot anything, this should be it. Better test this stuff

buddabrod · 2008-09-13 23:28:38

I'd like to see this integrated.. I love kde3 but sometimes I want so check some things out in kde4.

But thanks anyway for the great repo!

zeno0771 · 2008-09-19 07:32:49

tanis wrote:

@markc - thanks
As for KDE3/KDE4 issue... I like Qt4, I use it as a programmer, and I hoped KDE4 would be great. I'm not sure yet if I like the direction it took,
but in current shape - I don't like it for sure. It doesn't offer me anything I would need or like that is not present in KDE3, but in many ways KDE3 is superior - faster, more stable, hiding panels, file previews on desktop and many many other little things. That's why I moved back to KDE3 and I must say, that was relief. I have no idea what KDE's devs intent to do about 3.5 line,
but I would like KDE 3.5 to live at least for a while longer. Changing dependencies, especially gcc/glibc is a problem. If KDE's devs don't want to continue maintaining it, I think it would be great if we could gather a few people willing to do that. I wouldn't call it 3.6 (or "fork") though, since it would be maintaining only (unless someone wants to start adding new stuff, but I doubt it).
If there is a need for keeping KDE 3.5 alive, I could (and would love to) participate as well, as a programmer and as a packager for Arch
Having said that, I think that there are many people feeling the same about KDE 3.5 vs 4, so I guess there should be some more official initiative of that kind. If not, Arch community would be great starting point for something like that

AFAIK the KDE3 line stops here; 3.5.10 was expected to only be a maintenance release until the devs felt kde4 is ready for prime-time (the KDE forum already has tons of pages of people arguing about it so I won't go too far OT with that )
I'm not a coder but I'll beta-test any project that comes out of the "ashes" of KDE3 happily and I'm new to Arch so I'm the guy to do it!:lol: Thinking about it at work today, it would be interesting to see KDE3 actually branch off on its own development path instead of being left to die on the vine; there's still some potential and a whole bunch of usefulness left in it. So what if it's "old code"...like Linux was just invented a year ago?
More generally, I suppose *eventually* KDE devs will get around to hiding the taskbar, tweaking folderview, and either revamp or get rid of Dolphin, but I sometimes wonder if we KDE3 holdouts are just a vocal minority and the rest of the world really likes a Vista/Mac mutant hybrid-

zeno0771 · 2008-09-21 09:00:22

Heeeeeeyyyyyy, lookie what I found....:
http://www.kde-forum.org/index.php?page … #post70770
This guy's talking about doing what markc mentioned (and I think would be a good idea), namely forking KDE3.
Hey, it could happen...:D

markc · 2008-09-21 10:31:23

@zeno0771: interesting. It seems there is enough interest in a KDE3 fork for one to survive. I wish some group or cartel of folks would go ahead and do it other than some frustrated individuals just using the four letter word. I hope tanis, and others, don't mind a bit of a rant by me on the subject but I guess this issue does relate to a possible future of KDE 3.5.10. So far I haven't seen anything even vaguely like an outline of a plan or proposal to actually either fork, or work within the KDE core community towards a v3.5.11+, so this is what I would do at a minimum, more effort by more folks could be a lot more sophisticated, but this is a minimum...

1. secure an affordable independent vhost, perhaps a VPS would be enough to start with
2. import the KDE 3.5.10 stable branch into a Git repo, drop SVN support altogether
3. pull Git repo onto i686 and x86_64 platforms and confirm the Git repo builds for ArchLinux
4. fix any build issues and perhaps some simple obvious bugs along the way
5. prepare a set of reference tarballs called something like KDE-3.5.10-prefork
6. decide on a new name and domainname for the project, apply to vhost
7. install PunBB and hack it so the first post in any thread can be edited by anyone subscribing to the thread (semi-wiki'ish)
8. set up the forum code to handle announcements, bugs and feature requests, and various support forums (ie; don't use specialist bug, blog or wiki software)
9. encourage non-ArchLinux distro builders to build binary packages from the prefork reference tarballs, confirm stability
10. provide an unambiguous system to define the needed dependencies for a successful build (perhaps a simple text file listing version and sources)
11. search and replace and relabel the Git master branch and start accepting new patches for FoobarDE v3.6.0
12. start changing the build system to use Cmake, following the KDE4 path (except using Git instead of Subversion from the start)
13. apply a strict "always xmas in trunk" rolling release strategy so that a git checkout will ALWAYS build a stable set of binary packages
14. allow and encourage any number of developer orientated experimental branches that can be merged into the official "next" branch
15. the only governance should be a well known small group of trusted maintainers that provide gatekeeper judgement calls on what next patches go into the master stable branch
16. goto 15

I suggest a VPS (or Xen based host) because they can start out cheap and can be easily migrated to larger systems, with more ram and bandwidth, as and when needed. I'd also suggest trying to keep the entire communication and management system in one MySQL database via a single PHP frontend web interface and a mildly hacked PunBB is something I could envisage being doable. Obviously there could be many higher levels of sophistication and variations applied to these points but what I am suggesting is the simplest approach and absolute minimum required, IMHO, to become a viable ongoing project. Well, put it this way, if someone else roughly followed the above guidelines then I, for one, would be interested in contributing.

zeno0771 · 2008-09-21 21:46:48

Wow, you've put a lot of thought into this already
I have linked this over at that KDE forum thread that I linked to here...whoever that guy is, he's getting a lot of grief over there, but a couple of others are catching his drift so maybe if everyone can get on the same page (the LAST thing we need is competing KDE forks!!!)...Hope I didn't p!$$ anyone off by cross-linking but what I see right now is that organization is key, and you can't have organization with everyone running in different directions. I've got new-version fresh installs of VMware Workstation and VirtualBox (it does 64-bit now!:D) and a spare machine I use for just this sort of thing; also my own web page to get the word out, assuming anyone reads it anymore. I don't know if I can mirror since Comcrap has a new 250GB cap (my personal page is remote-hosted). Any other way I can help just let me know-

Last edited by zeno0771 (2008-09-21 22:13:06)

blackbelt_jones · 2008-09-21 22:18:53

zeno0771 wrote:

Hope I didn't p!$$ anyone off by cross-linking but what I see right now is that organization is key, and you can't have organization with everyone running in different directions.

Well, you sure didn't piss me off! I could kiss you! Anyway, lately, that particular forum has consisted of me and my buddy, seek-you , who I'm pretty sure is spambot.

Been talking about this a lot over the past 24. Here are the links:

http://www.kde-forum.org/artikel/20973/ … -fork.html
http://justlinux.com/forum/showthread.p … did=151982

blackbelt_jones · 2008-09-21 22:28:35

As you can tell, my concern is Konqueror, and I intend to concentrate on those packages that contain konqueror.

God knows how many KDE forks are being discussed and considered right now. For the moment, I think we should all just do what we're doing, but keep in touch. Anyone who wants to support my efforts, all they have to is follow me at twitter:

http://www.twitter.com/blackbelt_jones

zeno0771 · 2008-09-21 22:34:18

Oh, and my vote for a new name if it becomes a fully separate and distinct desktop?

L-Desk.

(The hyphen is optional.)

Here's my rationale: the original windowing system developed for the V operating system (the one from Stanford, not Unix System V) was appropriately called W; it's successor was...wait for it...the X window system we all use now.

We're talking about a fork of the K Desktop Environment, ergo..."L"...

"LDE" would be a little too obvious (and IMHO sounds like some kind of drug or emotional disorder).

Arch Linux

#26 2008-08-28 07:57:00

Re: KDE 3.5.10 repository

#27 2008-08-28 08:03:38

Re: KDE 3.5.10 repository

#28 2008-08-28 15:42:04

Re: KDE 3.5.10 repository

#29 2008-08-28 16:56:58

Re: KDE 3.5.10 repository

#30 2008-08-28 16:59:26

Re: KDE 3.5.10 repository

#31 2008-08-28 17:04:25

Re: KDE 3.5.10 repository

#32 2008-08-28 17:07:05

Re: KDE 3.5.10 repository

#33 2008-08-28 17:42:42

Re: KDE 3.5.10 repository

#34 2008-08-29 04:27:32

Re: KDE 3.5.10 repository

#35 2008-08-29 17:22:17

Re: KDE 3.5.10 repository

#36 2008-08-31 17:26:00

Re: KDE 3.5.10 repository

#37 2008-08-31 17:33:38

Re: KDE 3.5.10 repository

#38 2008-08-31 17:51:30

Re: KDE 3.5.10 repository

#39 2008-08-31 17:59:41

Re: KDE 3.5.10 repository

#40 2008-08-31 18:06:32

Re: KDE 3.5.10 repository

#41 2008-09-01 09:09:20

Re: KDE 3.5.10 repository

#42 2008-09-01 20:43:09

Re: KDE 3.5.10 repository

#43 2008-09-13 23:28:38

Re: KDE 3.5.10 repository

#44 2008-09-19 07:32:49

Re: KDE 3.5.10 repository

#45 2008-09-21 09:00:22

Re: KDE 3.5.10 repository

#46 2008-09-21 10:31:23

Re: KDE 3.5.10 repository

#47 2008-09-21 21:46:48

Re: KDE 3.5.10 repository

#48 2008-09-21 22:18:53

Re: KDE 3.5.10 repository

#49 2008-09-21 22:28:35

Re: KDE 3.5.10 repository

#50 2008-09-21 22:34:18

Re: KDE 3.5.10 repository

Board footer