(old)Puppy Linux Discussion Forum

gulk wrote: 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.

Understood. So the .pet I have on megaupload is ready to go; caveat is people will need to install libevent to make use of it, or transmission-2.42.pet should be added to slacko repo.
Enjoy

Don't you give me that clever geek talk, I ran the transmission pet and got . . . eh . . . now what? Could not find libevent in ppm?

Lobster. I suppose you are good to try the version Michalis has posted. Attached here.

thanks pemasu, thanks guys
. . . transmission update accomplished

Lobster wrote:Don't you give me that clever geek talk, I ran the transmission pet and got

Code: Select all

# transmission
transmission: error while loading shared libraries: libevent-2.0.so.5: cannot open shared object file: No such file or directory
# 

. . . eh . . . now what? Could not find libevent in ppm?

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

It might also be a good time to update the wikka (http://puppylinux.org/wikka/compiling) with:
a) After strip, compressing with UPX (http://www.murga-linux.com/puppy/viewto ... 582#213761)
b) In case the ./configure does not handle a "DESTDIR" option, paco (http://paco.sourceforge.net/) is your best friend to trace the installed files

Since I'm starting to get the hang of it, I compiled a password manager app that I like because of its cross-platform capability.
The main app pet file is only 1MB (attached here).

The app runs on Qt >= 4.3; if you don't have it installed on your puppy, just run this 5.9 MB pet (will install libQtCore, libQtGui and libQtXml): http://www.megaupload.com/?d=WI7CC2Q4

went to Firefox
http://www.mozilla.org/en-US/firefox/aurora/

downloaded and expanded FF (FireFox) file to
/usr/lib/firefox
and dragged Firefox executable to desktop
. . . FF 11 nightly build seems to be Slacko compatible alright . . .

Thanks for pointing this out.

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

Spoke too soon... no matter what Firefox I install using Lobster's method, I lose flash capability. I am therefore stuck with Aurora 7.0.1 (no biggy, cause it's been stable so far).

Lobster, did you check youtube or http://www.adobe.com/software/flash/about/ to see if flash was still fonctional after your update?

I am just going to stand quietly in the corner with a triangular hat with a D on it . . .

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.

Eterm with dependencies.


http://www.eterm.org/

Eterm with dependencies.

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

Lobster wrote:

Eterm with dependencies.

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.

If loaded, it runs with "Eterm" & should be in /menu/Utilities

Many thanks jpeps, as I say I feel it was probably something else in memory, probably via transmission bit torrent.

Wait just a minute . . . I did access a Mac USB keydrive yesterday . . .
could my computer have been channeling a ghostly Jobs?

No worries. Thanks for compiling and info

Just got Compiz working (not perfectly - the windows had no 'outer bar' to close resize etc.) Wobbling and other effects working - this is on a nearly pristine install of Slacko 5.3.1

Lobster,

CatDude, stripe and I have Compiz working fine under Slacko-531.

Lobster wrote:Just got Compiz working (not perfectly - the windows had no 'outer bar' to close resize etc.) Wobbling and other effects working - this is on a nearly pristine install of Slacko 5.3.1

Compiz working fine

Thanks smokey
That seems most peoples experience. Not sure if my difficulties are AMD 64bit chip or ATI crystal drivers or my own incompetence.

Quite happy without compiz, so not too concerned . . .

Trying to find record my desktop or similar at the moment
. . . OK back to the search . . .

Lobster wrote:

Compiz working fine

Thanks smokey
That seems most peoples experience. Not sure if my difficulties are AMD 64bit chip or ATI crystal drivers or my own incompetence.

Quite happy without compiz, so not too concerned . . .

Trying to find record my desktop or similar at the moment
. . . OK back to the search . . .

http://www.smokey01.com/software/multim ... 6-i486.pet