Slacko Puppy 5.3.1 Released
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
If anyone wants - here is a tiny, 23 KB package of wbar, without the configuration tool.
I'm still working on my Slacko-based puplet (which includes this tiny package). I started modding Woof using a PET similar to 01micko's base_hacks, which removes many unneeded features from Woof, such as the pinboard, PupZip and many deprecated stuff (e.g lprshell, PuppyPDF). This also removes many of Woof's dependencies, such as ROX-Filer, AbiWord and nenscript.
My goals with this package are simple:
- Make Puppy independent of /etc/windowmanager, /usr/sbin/delayedrun and ROX-Filer.
- Remove legacy stuff, such as the Puppy 1.x to 2.x migration script. They're such a horrible waste of space.
- Make it easier to port Slacko to x86_64. I already started working on it; I have most of the packages needed ready.
I'm still working on my Slacko-based puplet (which includes this tiny package). I started modding Woof using a PET similar to 01micko's base_hacks, which removes many unneeded features from Woof, such as the pinboard, PupZip and many deprecated stuff (e.g lprshell, PuppyPDF). This also removes many of Woof's dependencies, such as ROX-Filer, AbiWord and nenscript.
My goals with this package are simple:
- Make Puppy independent of /etc/windowmanager, /usr/sbin/delayedrun and ROX-Filer.
- Remove legacy stuff, such as the Puppy 1.x to 2.x migration script. They're such a horrible waste of space.
- Make it easier to port Slacko to x86_64. I already started working on it; I have most of the packages needed ready.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
consider using pstrip and upxgulk wrote: Well, I built transmission v2.42, but the executable is 18MB... does anyone have advice to reduce that somehow?
http://puppylinux.org/wikka/compiling (appendix4 in particular)
http://www.murga-linux.com/puppy/viewto ... 582#213761
Quite amazing... the transmission exe went from 18MB down to 270kB, using strip, then upx.Lobster wrote:consider using pstrip and upx
The executable runs fine on my machine, but I had previously installed transmission 2.13 from the PPM. I manually replaced the 2.13 executable with this one and it works. However I feel this is the dirty way to do it.
I would like to make a "clean" PET, but unfortunately, I have no way to make install in a specific folder (i.e. /dev/shm/transmission, per wikka instruction), then dir2pet. I don't know what files exactly were installed to the file system so I can manually get them back in a folder and dir2pet from there. Any idea? I'm sure this happened to you guys before me and you have a workaround.
In the mean time, if you're interested in transmission 2.42:
1) install the 2.13 PET from PPM (slacko repo)
2) overwrite transmission-gtk with the attached executable
Hi gulk,
Glad you seem to be enjoying Slacko.
When new2dir doesn't work for me I use a prog called Paco, though it looks like dev has ceased for the moment. It tracks installation and records it, and also can extract the package and make a tarball.
HTH
Glad you seem to be enjoying Slacko.
When new2dir doesn't work for me I use a prog called Paco, though it looks like dev has ceased for the moment. It tracks installation and records it, and also can extract the package and make a tarball.
HTH
Puppy Linux Blog - contact me for access
This is an understatement. That compiz package based on the dummy wm and lxpanel is wonderful; just add cube atlantis for pure show off!01micko wrote:Glad you seem to be enjoying Slacko.
Following your "paco" advice, I tracked down the transmission installation and "pacoball" put all that in a single folder. I manually moved files around to match puppy file system, reduced the executables size using strip and upx and ended up creating the attached transmission-2.42.pet (2.1MB, not bad at all... includes all bells and whistles too, like remote web interface, daemon, etc...) [edit]can't attach the file on the forum... file can be downloaded here http://www.megaupload.com/?d=KEEEUVP0[/edit].
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.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.
Puppy Linux Blog - contact me for access
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
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?
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
#
Just to be clear, according to Mick, libevent should have been automatically installed IF the transmission-2.42 pet was part of PPM.Lobster wrote: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?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 #
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
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
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
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 . . .
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
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?
Lobster, did you check youtube or http://www.adobe.com/software/flash/about/ to see if flash was still fonctional after your update?
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.
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.
- Attachments
-
- libuuid.so.1.3.0.pet
- (8.53 KiB) Downloaded 464 times
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Ay chihuahua!Eterm with dependencies.
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.Lobster wrote:Ay chihuahua!Eterm with dependencies.
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
If loaded, it runs with "Eterm" & should be in /menu/Utilities
- Attachments
-
- Eterm.png
- (100.35 KiB) Downloaded 1744 times