One more question: although I added libevent in the dependency list (i.e. +libevent), when I install the .pet in a pristine slacko (i.e. start in RAM), the .pet is installed but dependency is not... How do I force the dependency installation?
For example, if I install transmission-2.13 from the PPM, PPM would indicate the missing libs and and provide installation options.

This is a limitation of PPM. Just "clicking" on a pet doesn't check dependencies (say so in PetGet "help" too). We need to put in a feature request to BarryK as I agree that this is a shortcoming, deps are only checked when a pet is installed through the PPM interface._________________Woof Mailing List | keep the faith |

Just to be clear, according to Mick, libevent should have been automatically installed IF the transmission-2.42 pet was part of PPM.
Since it is not, you'll have to install libevent by hand separately (thanks Pemasu/Michalis for the libevent pet).

Bear with me while I'm on the learning curve, and thanks for trying the transmission.pet; I am glad it worked out in the end

I was actually wondering why Aurora was proposed when choosing Firefox in Slickpet. Aurora is the test bed for Firefox, and although it didn't give me any trouble, it is still considered a non-stable version.

I just followed Lobster's method to install the standard Firefox (v9.0.1 at the time of this writing):
1) download Firefox tarball
2) expand it
3) replace /usr/lib/firefox/ folder with the newly extracted /firefox/ folder

For future reference, rename, do not replace a folder.
That way, you have the original to fall back to.

The other method when testing a new release is to do a backup of your slackosave file using a utility like 2bytes Hot Backup for frugal PUPS.
Then each time you add something that is in test mode, you will have a dated, with time, backup that you can use to get back to where you were before the addition of the test software.

I had just got through downloading and installing SeaMonkey 2.6 from a PET package and before I installed the pet, I renamed /usr/llib/seamonkey directory to /usr/lib/seamonkey-bak. If the installed upgrade had given any problems, I could have just removed it and renamed that directory back to its original name.

Ay chihuahua!
Did not work for me and could not run from terminal or find eterm.
Just in case you had compiled for Saluki. I went into xfce4 and experienced (never seen this before) a white screen of death

It has now taken me almost 10 minutes to reinstall and setup Puppy to run from DVD as per usual (probably needed doing anyway)

Be interested in how others are getting on.
I think these issues may have been to do with transmission chugging away in the corner . . .

Ay chihuahua!
Did not work for me and could not run from terminal or find eterm.
Just in case you had compiled for Saluki. I went into xfce4 and experienced (never seen this before) a white screen of death

It has now taken me almost 10 minutes to reinstall and setup Puppy to run from DVD as per usual (probably needed doing anyway)

Be interested in how others are getting on.
I think these issues may have been to do with transmission chugging away in the corner . . .

Many thanks

Linux
as tested on Puppy's

I loaded it after pfix=ram, and it worked fine. I compiled in 5.3.1. I won't post a pet that clobbers any files in the original setup.