mkkde: create your custom KDE 3.5.5

Stuff that has yet to be sorted into a category.
Message
Author
User avatar
jason.b.c
Posts: 755
Joined: Wed 08 Feb 2006, 05:32
Location: Marshfield,MO
Contact:

#31 Post by jason.b.c »

I think i would certanly try this if i could get my puppy on the internet...
Puppy is Awesome..!!!!
[url=http://www.puppylinux.com/][img]http://www.browserloadofcoolness.com/sig.png[/img][/url]

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#32 Post by MU »

you need no internet to build KDE.
You only must download the required files before, but you could do that in Ubuntu or Windows, if your internet-connection works there.

Mark

Sir Savant
Posts: 9
Joined: Sun 31 Dec 2006, 20:46

#33 Post by Sir Savant »

I don't mean to kick this topic, but I don't want to crowd up the forum with a separate one.

I recently ran the mkkde script, and everything seemed to go well. I used that last list in the first post for my tgz. I moved the sfs file to "/mnt/home/" and then ran the DotPup file as required. Then I reboot, logged out of XFCE, and ran "startkde" A series of errors popped up, so I went into xfce, opened up a terminal, and tried to run "Kicker" but all it gives are errors. Any help?

Running Puppy 2.12

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#34 Post by MU »

you must run the dotpup after rebooting, not before.
Maybe you can fix it by installing it again.

If not, try these steps:
Boot WITHOUT the .sfs
Then delete these folders:
/initrd/pup_rw/opt
/initrd/pup_rw/usr/lib/qt
/initrd/pup_rw/usr/local/MU-XDG-activator

Then reboot WITH the .sfs.
Then install the dotpup again.


To say more, please post the errors you get (after these steps):
Run "Kicker" in the consolewindow.
Select the errormessages with the mouse, then middle-click in a forum-message to paste them.

Mark

shrdlu
Posts: 25
Joined: Wed 09 Nov 2005, 21:44
Location: NE Illinois

#35 Post by shrdlu »

Thanks, Mark.

This cleared up a problem I was having with KDEmini.

There were some broken symlinks in /usr/lib/qt/lib (to libqt-mt.so and libqt-mt.so.3 in /usr/lib/qt-3.3.6). I also added a symlink to libqt.so. Don't know if the last thing was needed but everything works now. :D

Best wishes!
If only I could be half as good as my dog thinks I am

User avatar
lickthefrog2
Posts: 57
Joined: Wed 22 Nov 2006, 18:30

#36 Post by lickthefrog2 »

Specifically re: BasKet
MU wrote: The gpgme-error appears, if you install the wrong gpgme with gslapt.
Be sure to use the version I mentioned above.
I also had tried another one before, and got the same error.

Mark
Hi Mark,

So I uninstalled with Gslapt the incorrect gpgme then installed the specific one you described: gpgme-1.0.3-i486-2df

But I'm still getting the error message. The more notes I make the more times the error comes up.

Any advice?

When you say install gpgme with gslapt, that's independent of KDE, right? Meaning, I don't put that package in with the other packages I'm using to customize my miniKDE?

And thanks again. I'm having fun (and only a little frustration) as a now-dedicated Linux user.

- lickthefrog2

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#37 Post by MU »

did you all these as suggested?:
attr 2.4.32_1-i486-1
acl 2.2.39_1-i486-1
libgpg-error1.4-i486-1df
gpgme 1.0.3-i486-2df

Yes, simply install with gslapt.
Uninstall old versions with it first.

Does that work?

Mark

User avatar
lickthefrog2
Posts: 57
Joined: Wed 22 Nov 2006, 18:30

#38 Post by lickthefrog2 »

No luck. Do I need to reboot after the uninstall before the reinstall?



The initial trouble I had, and why I tried it first with a different gpgme, is because I couldn't see the exact one you specified.

Since it didn't work, I went searching around and realized that I could add a different Gslapt Package Source.

After adding one or two, I then saw the correct gpgme and installed it with Gslapt.

The error message didn't go away, so I uninstalled mkkde and redid it.

Still the same problem.

I saw that gpgme was compiled with pth-2.0.7, so I'm going to try that.

User avatar
lickthefrog2
Posts: 57
Joined: Wed 22 Nov 2006, 18:30

#39 Post by lickthefrog2 »

DELETED

User avatar
lickthefrog2
Posts: 57
Joined: Wed 22 Nov 2006, 18:30

mkkde in Muppy 007

#40 Post by lickthefrog2 »

Hi,

I set up my own mkkde in Muppy007 as I am upgrading and starting from a clean slate.

I set up BasKet Note Pads in my KDE on Muppy006 but was getting an error message. Mark, you suggested that I install 4 Slackware packages with gslapt:

attr 2.4.32_1-i486-1
acl 2.2.39_1-i486-1
libgpg-error1.4-i486-1df
gpgme 1.0.3-i486-2df

Whereas in Muppy006, I might have made a mistake with gpgme, this time I didn't.

So I'm thinking there's something else I'm missing. How can I find out?

Everything else is great. Thanks again.

-lickthefrog2

sml
Posts: 162
Joined: Tue 10 Jan 2006, 02:56

#41 Post by sml »

What has happened to the dotpups.de server? I cannot reach it :(

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#42 Post by MU »

It moved to a new server.
It is back in some hours, when the DNS servers were updated.
Meanwhile use:
http://puppyfiles.org/dotpupsde/files/
http://puppyfiles.org/dotpupsde/dotpups/

Or this tool:
http://puppyfiles.org/dotpupsdelink.php

Mark

zsero
Posts: 16
Joined: Sun 18 Feb 2007, 15:56

#43 Post by zsero »

I have installed the mini KDE sfs&dotpup package, and I'm happily living using it. But now, I need to install KDevelop. What should I do now? Is it possible to integrate a downloaded KDevelop package into the already installed KDE package, or I shell make my whole new KDE package?

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#44 Post by MU »

If it is a .tar.gz from slakware, you could try to install it with gslapt.

But I think the cleaner way is to add it to the folder with the KDE-.tar.gz files and run mkkde again.
Then it will be added to the new .sfs, and the new dotpup will delete any .wh files in the folders it installs to.
Those .wh files are a bug from unionfs, so if you encounter problems when installing with gslapt, create a new kde.sfs.

Mark

orbisvicis
Posts: 42
Joined: Wed 07 Mar 2007, 01:09

#45 Post by orbisvicis »

Where are the kde environment variables? I can't seem to find them. Specifically the one that starts kwin.

orbisvicis

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#46 Post by MU »

If you run KDE as full desktop:
/opt/kde/bin/startkde
/opt/kde/bin/startkde2

Or if you run apps from another desktop:
/usr/local/KDE-3.5.5/Kicker

Mark

orbisvicis
Posts: 42
Joined: Wed 07 Mar 2007, 01:09

#47 Post by orbisvicis »

Reading startkde2 I assume if I place a file kdewm.sh in ~/.kde with the contents "export KDEWM=beryl-manager" and make it executable, a new environment variable should be created.
after startup however "terminal>env" does not list KDEWM, furthermore kwin still initializes.

What am I missing?

sincerely,
orbisvicis

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#48 Post by MU »

you might put it in the beginning of /root/.xinitrc or add it to startkde.
startkde is my own script, as I had to set some settings for Puppy, and did not want to alter the original startkde. So I renamed that to startkde2, and run it from the new startkde.

Mark

orbisvicis
Posts: 42
Joined: Wed 07 Mar 2007, 01:09

#49 Post by orbisvicis »

very nice!
i just stuck "export KDEWM=beryl-manager" into startkde with all the other exports and kwin no longer starts.
Just a note, kde doesnt seem to load anything in .xinitrc
http://murga-linux.com/puppy/viewtopic. ... 831#104831
This helps well

thanks,
orbisvicis

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#50 Post by MU »

I think .xinitrc has in the beginning somewhere

Code: Select all

if [ $CURRENTWM == "startkde" ];then
  exec startkde
fi
Or similar.
That was made to avoid, that for example ROX starts with KDE.

It seems it was removed in Puppy 2.14, but 2.11 or 2.12 still had it I think.

So you had to put stuff before that part.
However, using startkde is just fine, too :)
It might be even better, as with Puppys systemfiles like .xinitrc there is always the risk, that it will be overwritten by an upgrade or so.

Mark

Post Reply