mkkde: create your custom KDE 3.5.5
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
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
after startup however "terminal>env" does not list KDEWM, furthermore kwin still initializes.
What am I missing?
sincerely,
orbisvicis
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
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
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
I think .xinitrc has in the beginning somewhere
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
Code: Select all
if [ $CURRENTWM == "startkde" ];then
exec startkde
fi
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
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
Same way as you do with the devx_21x.sfs:
http://www.murga-linux.com/puppy/viewtopic.php?t=12904
Mark
http://www.murga-linux.com/puppy/viewtopic.php?t=12904
Mark
this might work without any changes, but I did not try yet::
ftp://ftp.fu-berlin.de/pub/unix/X11/gui ... Slackware/
Mark
ftp://ftp.fu-berlin.de/pub/unix/X11/gui ... Slackware/
Mark
I found the right tgz files
I found all the right tgz files I think
dloaded a fresh copy of mkkde
put the tgz files in the tgz dir
changed uselocal to no
then opened a rxvt
entered
can anyone help me where I went wrong? all I get is
- amarok-1.4.3-i486-4.tgz
arts-1.5.5-i486-1.tgz
k3b-0.12.17-i486-1.tgz
kdeaccessibility-3.5.5-i486-1.tgz
kdeaddons-3.5.5-i486-1.tgz
kdeadmin-3.5.5-i486-1.tgz
kdeartwork-3.5.5-i486-1.tgz
kdebase-3.5.5-i486-1.tgz
kdebindings-3.5.5-i486-1.tgz
kdeedu-3.5.5-i486-1.tgz
kdegames-3.5.5-i486-1.tgz
kdegraphics-3.5.5-i486-1.tgz
kdelibs-3.5.5-i486-1.tgz
kdemultimedia-3.5.5-i486-1.tgz
kdenetwork-3.5.5-i486-1.tgz
kdepim-3.5.5-i486-1.tgz
kdesdk-3.5.5-i486-1.tgz
kdetoys-3.5.5-i486-1.tgz
kdeutils-3.5.5-i486-1.tgz
kdevelop-3.3.5-i486-1.tgz
kdewebdev-3.5.5-i486-1.tgz
dloaded a fresh copy of mkkde
put the tgz files in the tgz dir
changed uselocal to no
then opened a rxvt
entered
Code: Select all
./mkkde
opt/kde/include/
opt/kde/include/kommanderplugin.h
opt/kde/include/kommanderfactory.h
opt/kde/include/kommanderwidget.h
opt/kde/include/kommander_export.h
usr/
usr/doc/
usr/doc/kdewebdev-3.5.5/
usr/doc/kdewebdev-3.5.5/README
usr/doc/kdewebdev-3.5.5/AUTHORS
usr/doc/kdewebdev-3.5.5/INSTALL
usr/doc/kdewebdev-3.5.5/ChangeLog
usr/doc/kdewebdev-3.5.5/COPYING
install/
install/doinst.sh
install/slack-desc
--- wait, processing slackware-installscript...
--- done - installscript
--- moving files
loong puse
r/doc/kdewebdev-3.5.5/INSTALL
usr/doc/kdewebdev-3.5.5/ChangeLog
usr/doc/kdewebdev-3.5.5/COPYING
install/
install/doinst.sh
install/slack-desc
--- wait, processing slackware-installscript...
--- done - installscript
--- moving files
--- removing locale-files
--- adding other files like libxine and ruby
--- creating dotpup
mkdir: cannot create directory `/mnt/hdb6/mkkde/dotpup/KDE-3.5.5/FILESYSTEM': File exists
mkdir: cannot create directory `/mnt/hdb6/mkkde/dotpup/KDE-3.5.5/FILESYSTEM/opt': File exists
mkdir: cannot create directory `/mnt/hdb6/mkkde/dotpup/KDE-3.5.5/FILESYSTEM/opt/kde': File exists
mkdir: cannot create directory `/mnt/hdb6/mkkde/dotpup/KDE-3.5.5/FILESYSTEM/opt/kde/bin': File exists
#another pause while dotpup window opens
entered info in first post
usr/doc/kdepim-3.5.5/.kde355.dot
usr/doc/kdesdk-3.5.5/
usr/doc/kdesdk-3.5.5/.kde355.dot
usr/doc/kdetoys-3.5.5/
usr/doc/kdetoys-3.5.5/.kde355.dot
usr/doc/kdeutils-3.5.5/
usr/doc/kdeutils-3.5.5/.kde355.dot
usr/doc/kdevelop-3.3.5/
usr/doc/kdevelop-3.3.5/.kde355.dot
usr/doc/kdewebdev-3.5.5/
usr/doc/kdewebdev-3.5.5/.kde355.dot
usr/man/
usr/man/.kde355.dot
usr/man/man3/
usr/man/man3/.kde355.dot
usr/include/
usr/include/.kde355.dot
usr/include/python2.4/
usr/include/python2.4/.kde355.dot
usr/share/
usr/share/.kde355.dot
usr/share/applications/
usr/share/applications/.kde355.dot
usr/share/applications/KDE-3.5.5.desktop
usr/share/icons/
usr/share/icons/.kde355.dot
usr/share/desktop-directories/
usr/share/desktop-directories/.kde355.dot
usr/etc/
usr/etc/.kde355.dot
usr/etc/xdg/
usr/etc/xdg/.kde355.dot
usr/etc/xdg/menus/
usr/etc/xdg/menus/.kde355.dot
KDE-3.5.5/
KDE-3.5.5/icon.xpm
KDE-3.5.5/KDEpanel.png
KDE-3.5.5/Kicker
KDE-3.5.5/killkicker
KDE-3.5.5/killkicker.png
KDE-3.5.5/resource/
KDE-3.5.5/resource/postinstall.sh
tar: --exclude=FILESYSTEM: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors
cp: cannot stat `KDE-3.5.5/resource/prepreinstall.sh': No such file or directory
cp: cannot stat `KDE-3.5.5/resource/preinstall.sh': No such file or directory
md5sum: prepreinstall.sh: No such file or directory
md5sum: preinstall.sh: No such file or directory
zip warning: name not matched: prepreinstall.sh
zip warning: name not matched: preinstall.sh
adding: dotpup.sh (deflated 73%)
adding: size.txt (stored 0%)
adding: sizefilesystem.txt (stored 0%)
adding: md5sum.txt (deflated 35%)
adding: gauge.pb (deflated 57%)
adding: checkspace.pb (deflated 32%)
adding: dfree.sh (deflated 41%)
adding: space.sh (deflated 89%)
adding: space2.sh (deflated 89%)
adding: pbexeccmd.pb (deflated 37%)
adding: KDE-3.5.5.tbz (stored 0%)
adding: wxbmenue.rc (stored 0%)
adding: config.files (stored 0%)
adding: FILESYSTEM.tbz (deflated 2%)
--- creating squashfs
Parallel mksquashfs: Using 1 processor
Creating little endian 3.0 filesystem on KDE355mini_2xx.sfs, block size 65536.
Little endian filesystem, data block size 65536, compressed data, compressed metadata, compressed fragments
Filesystem size 229213.83 Kbytes (223.84 Mbytes)
46.89% of uncompressed filesystem size (488829.52 Kbytes)
Inode table size 431094 bytes (420.99 Kbytes)
30.44% of uncompressed inode table size (1416012 bytes)
Directory table size 428140 bytes (418.11 Kbytes)
49.85% of uncompressed directory table size (858930 bytes)
Number of duplicate files found 3466
Number of inodes 43635
Number of files 39850
Number of fragments 3056
Number of symbolic links 723
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 3062
Number of uids 1
root (0)
Number of gids 1
unknown (99)
--- cleaning up
---------------------------------
finished! now rename KDE355mini_2xx.sfs to a valid name matching your Puppy, like KDE355mini_210.sfs
your dotpup is in /root/dotpup-wizard/
it creates a dotpup and a 237meg sfs after I mount the sfs and run the dotpup
when i reboot and run xwin startkde it informs me no
kstartup config file found check installation and refuses
to start and when in icewm kicker refuses to run
problem exists between keyboard and chair! I ran the .wh. remover script and all my probs went
away!
when i reboot and run xwin startkde it informs me no
kstartup config file found check installation and refuses
to start and when in icewm kicker refuses to run
problem exists between keyboard and chair! I ran the .wh. remover script and all my probs went
away!
-
- Posts: 6
- Joined: Wed 06 Jun 2007, 02:16
Hi Mark, Guten Tag!
I've got a question for you after reading through a great deal of this thread: I have your GSlapt.pup installed and it's been working really great for me in getting a lot of software for my HDD install (not frugal---full HDD) of Puppy 2.17 onto a 10gig partition. I also have WhoDo's EZpup2.17RC2, so I'm using IceWM by default for a window manager.
I've added extra repos to GSlapt so that I span Slacky from 10.2 up to 12, using a list brought over from another Slacky-based install. It's worked great.
Now I'm curious and here's the question: I've done many successful installs of KDE upon non-KDE distros, like Wolvix and VectorLinux Gold (plus others), and I'm wondering if it would be possible to do such a KDE install upon such a minimal install as Puppy 2.17 straight from GSlapt? Or do you think this wouldn't work like it does in these other distros? Only Vector has the "one file grabs all" system in their GSlapt---all the other installs I've had to select each and every package and yes... despite my connection I still go make coffee. So I do realise there's "a lot to it".
Even you must start from "somewhere", jah? Do you compile your entire KDE desktop or just download from Slacky repo Mark?
I'm very excited to read your thoughts upon this idea!
Mazzel! mfg!
Eyes-Only
"L'Peau-Rouge"
I've got a question for you after reading through a great deal of this thread: I have your GSlapt.pup installed and it's been working really great for me in getting a lot of software for my HDD install (not frugal---full HDD) of Puppy 2.17 onto a 10gig partition. I also have WhoDo's EZpup2.17RC2, so I'm using IceWM by default for a window manager.
I've added extra repos to GSlapt so that I span Slacky from 10.2 up to 12, using a list brought over from another Slacky-based install. It's worked great.
Now I'm curious and here's the question: I've done many successful installs of KDE upon non-KDE distros, like Wolvix and VectorLinux Gold (plus others), and I'm wondering if it would be possible to do such a KDE install upon such a minimal install as Puppy 2.17 straight from GSlapt? Or do you think this wouldn't work like it does in these other distros? Only Vector has the "one file grabs all" system in their GSlapt---all the other installs I've had to select each and every package and yes... despite my connection I still go make coffee. So I do realise there's "a lot to it".
Even you must start from "somewhere", jah? Do you compile your entire KDE desktop or just download from Slacky repo Mark?
I'm very excited to read your thoughts upon this idea!
Mazzel! mfg!
Eyes-Only
"L'Peau-Rouge"
*~*~*~*~*~*
Proud user of LXpup and 3-Headed Dog.
*~*~*~*~*~*
Proud user of LXpup and 3-Headed Dog.
*~*~*~*~*~*
Bonsoir
I simply downloaded the KDE-packages from Slackware with a browser.
Then my build-script extracts them, and runs the included "install" script (it copies it one folder up first).
This script usually just creates some symbolic links.
Then my script builds the .sfs from these extracted and "modified" folders.
That's it basically, however then some detail-work is added.
First, I ran some applications like konqueror from a consolewindow.
This showed me some missing dependencies, so I also downloaded and added those.
Then I modified "startkde".
I don't exactly remember what I changed, I think I modified things like some XDG environment variables.
These are for menu-generation, but I think also for other settings.
Without these changes, KDE got confused, and for example konqueror would not remember its bookmarks on next startup.
My changes might not be needed, if you'd run KDE as full desktop (not using JWM or Icewm as windowmanager).
But for me it was important to be able to run KDE-applications from within Puppys standard desktop.
So as conclusion:
It definately is wort a try to play around a bit.
Just on a harddisk-installation it always is quite risky to "break" things, so I'd suggest to try it with a frugal installation or boot from CD.
Then you can restart from scratch, if too many weird things happen.
Best wishes mon ami, aussi to the calm, wide landscape where you live, and where things are less hectic than here (at least I image it like that)
Mark
I simply downloaded the KDE-packages from Slackware with a browser.
Then my build-script extracts them, and runs the included "install" script (it copies it one folder up first).
This script usually just creates some symbolic links.
Then my script builds the .sfs from these extracted and "modified" folders.
That's it basically, however then some detail-work is added.
First, I ran some applications like konqueror from a consolewindow.
This showed me some missing dependencies, so I also downloaded and added those.
Then I modified "startkde".
I don't exactly remember what I changed, I think I modified things like some XDG environment variables.
These are for menu-generation, but I think also for other settings.
Without these changes, KDE got confused, and for example konqueror would not remember its bookmarks on next startup.
My changes might not be needed, if you'd run KDE as full desktop (not using JWM or Icewm as windowmanager).
But for me it was important to be able to run KDE-applications from within Puppys standard desktop.
So as conclusion:
It definately is wort a try to play around a bit.
Just on a harddisk-installation it always is quite risky to "break" things, so I'd suggest to try it with a frugal installation or boot from CD.
Then you can restart from scratch, if too many weird things happen.
Best wishes mon ami, aussi to the calm, wide landscape where you live, and where things are less hectic than here (at least I image it like that)
Mark