(old)Puppy Linux Discussion Forum

SEE NEXT POST FOR UPDATED GLIB it is REQUIRED

This was a challenge to say the least, but finally here is my Midori build that is specially configured for Puppy, the only thing removed from the main package are locales and some large extensions that link against webkit

the 2.5MB pet package (static webkit, libsoup - no SSL) is here
http://puppy-development.googlecode.com ... 2.2-92.pet

if you are going to include this in a minimal puplet and remove seamonkey - you should use flashplayer9 because some of the flash10 dependencies are in the seamonkey directory (nss and nspr)

full shared build including all the Xtras including gnutls, libsoup, libwebkit and all extensions = 5MB
http://puppy-development.googlecode.com ... 2.2-93.pet

the pet has a upx'd binary
here is a 2.2MB pxt (xz compressed) without upx
http://puppy-development.googlecode.com ... 2.2-92.pxt

cookie-manager, web-cache, feed-panel, adblock and formhistory were all remove for size (8MB each from static linking) I filed a bug report about the initial build failures and tacked on a feature request for "builtin" extensions (like the new abiword has)

REQUIRES updated GLIB (for libsoup)
uploading to google code

Lighthousepup latest. Midori crashes:
bash-3.00# midori

(midori:12361): Gtk-WARNING **: Error loading theme icon 'stock_new-tab' for stock: Icon 'stock_new-tab' not present in theme

(midori:12361): Gtk-WARNING **: Error loading theme icon 'gnome-stock-trash' for stock: Icon 'gnome-stock-trash' not present in theme
Segmentation fault
<root> ~

did you install the updated glib?

Yes. I installed it first and then Midori. And then I removed them and installed them in different order. Maybe reboot would help, but also something maybe is really missing...

I'd have to try it on lighthouse - not sure what libraries it has by default - Is it based on 4.2.X?

Wow, this is unbelievable! Thank you!

So how do I get SSL to work?

Did you compile without NSS at all or is it looking for it somewhere?

It looks like https will require gnutls which has many dependencies because libsoup dropped support for straight openssl and webkitgtk dropped support for using curl instead of libsoup back in march of last year (I think origyn web browser forked the curl setup)... this seems to be case of buntuism... so it may be a while for secure browsing (gnutls is hard enough to build as it is)

On a separate note
more failures of the waf build system
- it decided to use -pthread instead of -gthread
- it "found" several libs in /usr/X11R7/lib that were in /usr/lib
- drops linkages on static libraries for its dependencies
- it hides the build info by default or in verbose it doesn't show what is REALLY happening
- it requires python
- it hides the config info in a hidden folder

WAF is not ready for this kind of operation - when it finally works 99.9% - then think about hiding stuff by default

Please use autoconf etc... - it works fine and when it doesn't you can at least fix the problem without a chainsaw - I'd rather edit makefiles than use waf

enough ranting about waf - next time I build it I will dump everything to a single directory and try to build it with a single gcc command using -fwhole-program (if possible I will try to build in the extensions to the midori binary)

So here is the plan:
update openssl (shared) required by the version of gnutls that is required by libsoup that is required by webkitgtk-1.1.19(first version that supports glib instead of libICU ~16MB)
build the rest statically while tracking the dependencies manually so that I can manually link them in easier

Lighthousepup 443F is based on Puppy 4.3.1. Well I am using Mariner sfs and KDE sfs and they include quite a lot of apps and libraries to basic installation. So the soup is more complex I figure. I use extra apps mostly by sfs, so I havent installed extra libs manually. Only your glib.

I could try Minori pfix=ram installation when I have time.

I rebuilt everything including gnutls as shared and stripped out all but the libs that are required and packaged them into the Midori pet (I am assuming that random files or executables will not be used - they usually aren't)... let me know

without further ado
http://puppy-development.googlecode.com ... Midori.pet

by the way - its still only 5MB including gnutls (+deps), libsoup, libwebkit and all of the extensions
NOTE: had to delete Midori's old folder in /root/.config/

Allright, replying from Midori so it works. I booted LHP443F with pfix=ram. Installed the latest Midori.pet, pet wasnt associated to petget, searched it and installed, didnt add itself to menu. From console:

bash-3.00# which petget
/usr/sbin/petget
<root> ~
bash-3.00# midori
bash: midori: command not found
<root> ~
bash-3.00# which midori
<root> ~

So the installation wasnt quite succesful. Then I installed the first Midori.pet (before upx or something version)

bash-3.00# which midori
/usr/bin/midori
<root> ~

And Midori works. So in my LHP443F Mariner sfs and KDE sfs or my savefile prevented Midori installation. But I couldnt install the latest succesfully. Could I try midori with latest Dpup ? Stardust will be tested when I have time also.

I knew I would forget something - The midori .desktop file in /usr/share/applications needs to be fixed to show up in the menu.

If you installed the static version, you may need to delete the /root/.config/Midori folder

afterwards you may want to edit preferences to enable spell check (enter en_US for us english) and you can enable the small icon theme and your choice of downloader amongst many other tweaks.

If you are using Dpup, you may want to separate the packages so that you can use the Debian versions of the libraries. (you can use pet2tgz followed by pupzip to remove them from /Midori/usr/lib then tgz2pet and petget to install)

I removed /root/.config/Midori everything. Then reinstalled latest static Midori.pet. It didnt add all the files to above folder. Also which Midori didnt find Midory binary on the beginning of my test. I downloaded latest Midori.pet with Uget to be sure of getting it right but no go with it. So cant get SSL support with latest Midori. I believe there is something wrong with the latest static Midori.pet or my LHP443F with pfix=ram is really allergic to it. Quite possible remembering my first failure.

Ps. Latest Midori.pet creates /root/.config/Midori and three files inside it:
confic, running and midori_socket.... but no midori binary to /usr/bin

It also adds gnutls_min... to puppy package manager pet list but no Midori
But as I said, might be problem with my LHP only. Needs more testing, but now I dont have time. Later....

I didn't get a midori binary either with the Midori.pet.

Technosaurus, could you post the header files too? I want to replace Chrome in the next Puppeee beta with Midori, but I'll have to rebuild Pidgin against gnuTLS.

Just installed the 2.5 mb static version in quirky006 just for a test. It works pretty good. Am using it to post this.
Works well with privoxy 3.0.12(localhost:8118).
Occasionally I lose the scrollbar when maximised but returns when windowed and remaximised.
Live audio stream via flash is working as I post now and seamonkey is running concurrently.

ADDED for Dpup484b4:
In dpup484b4, one needs to place the symlinks to /lib/firefox/plugins in the /usr/lib/mozilla/plugins folder via: select all while in /lib/firefox/plugins, ctrl-shift-drag to /usr/lib/mozilla/plugins. Then all existing plugins are enabled and working. My /usr/lib/mozilla/plugins happened to be empty to begin with here, but other dpup systems may be different, so check it first.

While posting to forum, the processor would peg at 100% so had to kill. Trying now with JSCRIPT toggled off. This seems to eliminate the crashes from pressing back button as well.

Moans: using light house 4.3.3-f

I'll repackage it when I get home tonight along with gnutls and the header files - It was really late (or early) and I had to manually build the package because new2dir(installwatch) doesn't pick up waf installs... still - can't believe I missed the midori binary. I applied a patch to remove libIDN requirement from webkitgtk as well (the patch to allow glib instead of libICU is already applied in webkitgtk-1.1.19), so I'll post the -IDN patch too. I just ran out of time and got in a hurry.


Read the Midori website faq regarding the icons - you need a large appropriate icon theme (tango etc...) to remove the messages - should not affect operations though

I reposted the shared midori with the dependencies included - turns out I packaged my working directory by accident. Afterwards I noticed that the icon does not show up in the jwm menu (even though it is displayed in ROX and other window managers)

Fix:
replace the following line in /usr/share/applications/midori.desktop
Icon=midori
with
Icon=midori.png

This will be fixed in the split package.

I am running the first package .So far it plays well with e17 in Foxy 3. The only issue i have found is that you need to enter the url twice to add a page to the speed dial.