Puppy Linux Discussion Forum

[Béèm]

It doesn't work isn't very helpful.
You have to give details about what you see.

[Béèm]

[maxpro4u]

will you be including kmail soon?
how do you set konqueror as default browser? i had opera set as default before installing kde.

edit- i changed the file found here /usr/local/bin/defaultbrowser to konqueror.

[darkduck]

[peebee]

Hi darkduck

Did you keep the same pupsave after removing the earlier sfs's and starting with the latest?

I think you will need to start again with a clean pupsave......there is some residue in your old pupsave that is stopping the new kde starting.

From bitter experience I always try 1st a new pupsave, then a COPY of my old pupsave so I can always go back if there are problems. Takes a bit longer but is better for peace of mind.

Cheers
Peter

[Béèm]

I agree with peebee.
Always start with a fresh save file. (so pfix=ram on first boot)

[Iguleder]

Tomorrow I think I'm going to start the trinitypup experiment, but I'm still not sure about the package sources - Debian Squeeze or Ubuntu Maverick. I want to try Ubuntu first (for its later X), I want to take a break from Debian

The SFS approach doesn't seem to work well, for many reasons:
1) KDE, in contrast with GNOME, is known for the superb integration between its applications and components, this means it's hard to package it in a modular way, since many parts of it are shared; different KDE packages share many dependencies, that's why KDE packages in package managers like APT are small. Most of the dependencies of KDE applications are either dependencies of the KDE core (things like the base KDE libraries, aRts/Phonon, Qt) or shared between many packages. Distros like Arch achieve modularity by using meta-packages. However, Puppy doesn't have this in its SFS extensions and packaging Trinity in PET packages is not a practical solution to this problem, since PPM is a weak package manager without meta-package functionality and because save files don't like the huge size of Trinity.
2) We're in the Woof age of Puppy, it's hard to make one set of packages for all 5th generation puppies.
3) SFSs are not user friendly.
4) SFSs are a very primitive way for package management. Since KDE has many dependencies, it causes problems. For example, if the KDE SFS has libroflzomg and the use wishes to compile the third-party KDE application Kroflzomg, he has no idea that this package is present on the system. That's confusing, install the package "libroflzomg" or "libroflzomg_DEV"?
5) It's hard to trim KDE; it uses exotic file types (for instance, .la files) for some things that normally go to the "exe" package. In other words, when you attempt to create a "DEV" package for KDE, you must keep those .la files in the main package, while with all other packages you do the opposite. This makes it a big effort to package KDE.

If you consider this, the modularity challenge and the compatibility issue, it becomes very clear why I'm so frustrated by this. I guess a Puppy that comes with Trinity built-in is the way to go.

[Béèm]

Iguleder, don't be frustrated.
We take Trinity as it comes.
I had instability also with a gnome version, a year of two ago.
Therefor I now install my programs outside the save file and being up and running again is a matter of minutes.

[maxpro4u]

[peebee]

I have solved the time problem when using Trinity on luci23x - there was a missing #!/bin/sh line in the settime file in /root/Startup.

If edited to:

[darkduck]

[peebee]

hi Darkduck

I don' know if this will make a difference but you should use the WM Switcher to activate Trinity......not the xwin command

Cheers
Peter

p.s. you can rename the pupsave files using puppy itself....

[darkduck]

[peebee]

If you have loaded the trinity-core sfs through the boot manager you should also have trinity in the list.

Sounds like you have something wrong.....

[darkduck]