installing "irridium browser" in puppylinux

[d_vineet]

Hi!
I am migrating from ubuntu to puppylinux.
Wish to install "irridium browser" from https://iridiumbrowser.de/downloads/linux.

It requires apt-get along with wget in command line.

Code: Select all

wget -qO - https://downloads.iridiumbrowser.de/ubuntu/iridium-release-sign-01.pub|sudo apt-key add -
cat <<EOF | sudo tee /etc/apt/sources.list.d/iridium-browser.list
deb [arch=amd64] https://downloads.iridiumbrowser.de/deb/ stable main
#deb-src https://downloads.iridiumbrowser.de/deb/ stable main
EOF
sudo apt-get update
sudo apt-get install iridium-browser

However, apt-get is not available in puppylinux.

Help is requested regarding how to install "irridium browser" in puppylinux.

Thanks in advance.

[dancytron]

Puppy does not have apt-get.

Download the .deb file. Assuming you are on a 64 bit ubuntu based puppy, it is here.
https://downloads.iridiumbrowser.de/ubuntu/

Click on it after you download it and it will install.

You may (probably will) have to figure out the dependencies after that and since it is Chromium based also figure out how to either run it as spot or hack it to run as root. Others will be by to help you with that.

[d_vineet]

Great. Thanks for your instant reply.
I downloaded .deb and installed it by clicking it.
Now it appears in menu.
But if I try to run it from menu, nothing happens.
Pl. help me in figuring out how do I make it run.
Thanks.

[peebee]

64-bit only

Using xenialpup-64

In a terminal

cd /usr/lib/iridium-browser

run-as-spot ./iridium-browser

Works fine at first glance - no missing dependencies....

[dancytron]

Great. Thanks for your instant reply.
I downloaded .deb and installed it by clicking it.
Now it appears in menu.
But if I try to run it from menu, nothing happens.
Pl. help me in figuring out how do I make it run.
Thanks.

Run it from the terminal and see what message you get.

If you don't know the command, look in /usr/share/applications, find the *.desktop file, and look at the "exec" line.

Probably, you need to do this or something similar http://www.murga-linux.com/puppy/viewto ... d012f56dfe except with your command, not chrome.

Mike will be by sometime, he is the chrome expert.

[foxpup]

Let's see if you have missing dependencies.

Open a terminal, type

Code: Select all

ldd /usr/bin/iridium-browser

and look for missing libs in the output.

Another way, is to look in the Puppy menu for 'check dependencies'.

Then you can install these libs, and their dependencies (!), with the Puppy Package Manager. Be sure to update the PPM first.

Just another idea. If there are a lot of missing libs and you do not want to look for all of them, you could try if loading chromium would solve the missing depencies.
You can try it by loading a sfs of chromium from this thread: http://murga-linux.com/puppy/viewtopic.php?t=81351. I am not sure tho that this will work.

What Puppy are you migrating to?

[d_vineet]

64-bit only

Using xenialpup-64

In a terminal

cd /usr/lib/iridium-browser

run-as-spot ./iridium-browser

Works fine at first glance - no missing dependencies....

Wow... it worked. The browser opened.
But it left a traceback.

Code: Select all

root# run-as-spot ./iridium-browser
[27633:27633:0806/140843.988538:ERROR:browser_main_loop.cc(269)] GLib-GObject: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
[27633:27633:0806/140844.072639:ERROR:browser_main_loop.cc(269)] GLib-GObject: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
[27633:27633:0806/140844.072709:ERROR:browser_main_loop.cc(269)] GLib-GObject: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
[27633:27633:0806/140844.072759:ERROR:browser_main_loop.cc(269)] GLib-GObject: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(iridium-browser:27633): GLib-GIO-WARNING **: Tried to register an extension of the type (null) to extension point gio-native-volume-monitor. Expected type is GNativeVolumeMonitor.

(iridium-browser:27633): GLib-GIO-WARNING **: Tried to register an extension of the type (null) to extension point gio-volume-monitor. Expected type is GVolumeMonitor.

(iridium-browser:27633): GLib-GIO-WARNING **: Tried to register an extension of the type (null) to extension point gio-vfs. Expected type is GVfs.
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
[27731:27731:0806/140845.538311:ERROR:vaapi_wrapper.cc(313)] vaInitialize failed: unknown libva error
ATTENTION: default value of option force_s3tc_enable overridden by environment.
*** autoupdate was enabled, overriding with false
[27633:27735:0806/140846.937430:ERROR:bus.cc(394)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

(iridium-browser:27633): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Unknown or unsupported transport 'disabled' for address 'disabled:'[quote]

Whether it means that some dependencies are not taken care of?
Thanks.

[d_vineet]

Let's see if you have missing dependencies.

Open a terminal, type

Code: Select all

ldd /usr/bin/iridium-browser

and look for missing libs in the output.

Another way, is to look in the Puppy menu for 'check dependencies'.

Then you can install these libs, and their dependencies (!), with the Puppy Package Manager. Be sure to update the PPM first.

Just another idea. If there are a lot of missing libs and you do not want to look for all of them, you could try if loading chromium would solve the missing depencies.
You can try it by loading a sfs of chromium from this thread: http://murga-linux.com/puppy/viewtopic.php?t=81351. I am not sure tho that this will work.

What Puppy are you migrating to?

I am migrating to the latest puppy : xenialpup 7.5 CE.

The commandline as you advised gives following msg.

Code: Select all

root# ldd /usr/lib/iridium-browser
ldd: /usr/lib/iridium-browser: not regular file

In the meantime, I have installed chromium to see if it fixes the dependencies. But no luck.

[foxpup]

Code: Select all

ldd /usr/bin/iridium-browser

wrong place
"bin" and not "lib": it is a binary, not a lib

[foxpup]

In the meantime, I have installed chromium to see if it fixes the dependencies. But no luck.

I am not sure the 'traceback' is about dependencies.
And I am not sure the warnings matter, nor the errors, if the browser works well. I am not an expert on this.

[d_vineet]

Code: Select all

ldd /usr/bin/iridium-browser

wrong place
"bin" and not "lib": it is a binary, not a lib

tried it with the following result.

Code: Select all

root# ldd /usr/bin/iridium-browser
	not a dynamic executable

[d_vineet]

In the meantime, I have installed chromium to see if it fixes the dependencies. But no luck.

I am not sure the 'traceback' is about dependencies.
And I am not sure the warnings matter, nor the errors, if the browser works well. I am not an expert on this.

Many thanks for your help.
Just one more fine point--
How do I make it open from menu rather than from terminal?

[foxpup]

Code: Select all

ldd /usr/bin/iridium-browser

wrong place
"bin" and not "lib": it is a binary, not a lib

tried it with the following result.

Code: Select all

root# ldd /usr/bin/iridium-browser
	not a dynamic executable

It is a bash script!
I think the binary is in /usr/lib/iridium-browser/
So, try

Code: Select all

ldd /usr/lib/iridium-browser/iridium-brower

[Mike Walsh]

@ d_vineet:-

to the 'kennels'. Hope you'll enjoy your time with Puppy.

Iridium, eh? Mm.... I looked at this a while back, when it first appeared. It was available as an AppImage in those days, though even that required a fair bit of 'tweaking', as I recall.

Re: the 'traceback' stuff. Ignore it. We all do. Chromium-based browsers are incredibly 'noisy' in the terminal, and even when running perfectly, still spit out no end of guff. I believe The Chromium Project (a.k.a 'Big Brother' Google) designed it that way to make debugging easier for the dev team.....but it can be a bit off-putting to those not 'in the know'!

I've got some stuff to take care of this morning, so I won't be around for a bit.....but I'll have a look at this later on, and see if I can run you up a Menu Entry .pet that will let you start it from Menu->Internet.

Bear with me. BTW, any particular reason why you want to use Iridium, rather than one of the somewhat 'easier' Chromium 'clones'? (Which includes Chrome itself, believe it or not...) From what I understand, Iridium is supposed to be super-security-minded, in that it only runs from a location in /tmp for the duration of the session.....disappearing into thin air at shutdown.

Anyway, I'll get back to ya later.


Mike.

[d_vineet]

@ d_vineet:-

to the 'kennels'. Hope you'll enjoy your time with Puppy.

Iridium, eh? Mm.... I looked at this a while back, when it first appeared. It was available as an AppImage in those days, though even that required a fair bit of 'tweaking', as I recall.

Re: the 'traceback' stuff. Ignore it. We all do. Chromium-based browsers are incredibly 'noisy' in the terminal, and even when running perfectly, still spit out no end of guff. I believe The Chromium Project (a.k.a 'Big Brother' Google) designed it that way to make debugging easier for the dev team.....but it can be a bit off-putting to those not 'in the know'!

I've got some stuff to take care of this morning, so I won't be around for a bit.....but I'll have a look at this later on, and see if I can run you up a Menu Entry .pet that will let you start it from Menu->Internet.

Bear with me.


Mike.

Thanks Mike for offering a warm welcome to puppylinux. This gives me confidence to proceed with it.
I am really enjoying puppylinux.
I find it a lot easier than Ubuntu to configure and light weight like a feather to run.

Further, the community is very vibrant and helpful.
Love it.
Thanks.

p.s. (regarding why I am keen at using iridium:- because I don't wish to get tracked and eyed-upon by google-servers. I am also using duckduckgo privacy essentials addon for this reason).

[rufwoof]

As a long term FireFox user, I moved over to Iridium some weeks back now and love it. Predominately my daily boot is now just OpenBSD + iridium. I've also moved to a more minimalist desktop, run cwm that is a integral part of OpenBSD where you launch a exec prompt with a key combination, type the first two or thee letters of the program you want to run and press Enter. Maximise all windows and flip between them using alt-tab works for me, I also however have a hot corner that shows all windows when you mouse into that corner so you can left mouse to switch to a particular window or middle mouse to close a window. I run X under userid user, and use root to store personal data/docs - that I switch console to (Ctrl-Alt-Fn) and have that set to run tmux (along with mc). Nice colourful consoles that I can scroll, cut/paste and have multiple 'windows' (and panes within windows that you can zoom/unzoom if desired - but which personally I don't use). Leaves pretty much just a blank desktop, so I run iridium with multiple tabs (X/user) maximised, along with cli/root/tmux and multiple 'tabs' (windows) on two separate console sessions and just ctrl-alt-fn flip between them. As I like a visible desktop clock and as iridium is maximised I added a single tab that shows the date/time as its title (I store bookmarks in that tab so if I activate it I also have a list of links). The attached full screen snapshot is pretty much my X desktop i.e. iridium. Iridium's multi-media support seems very good, plays mp4's, views PDF's ...etc. very well.

Iridium is good at improving privacy whilst it works great. OpenBSD add additional security on top of that (Pledge and soon Unveil) https://marc.info/?l=openbsd-misc&m=152872551609819&w=2 With OpenBSD's simple/quick installation (9MB file if you use the http based install) the cli based install takes less than 5 minutes. Their man based documentation is great, specific to the install and any errors in text are considered as a bug comparable to any software bug. And the base OBSD includes the likes of X (more secure version), web server, mail server ...etc.etc. that's all security audited as a whole. Downside is that it does run slower (higher security and doing things properly), but still acceptable on my 10 year old system. They're also sticklers for doing things properly and visibility, so Blobs are out (less broad hardware support). Once bitten however the tendency seems to be that future hardware acquisitions are selected with the target OS in mind (at least it is for me i.e. any hardware I will add in future must work with OBSD for me to even contemplate buying it).

[d_vineet]

Code: Select all

ldd /usr/bin/iridium-browser

wrong place
"bin" and not "lib": it is a binary, not a lib

tried it with the following result.

Code: Select all

root# ldd /usr/bin/iridium-browser
	not a dynamic executable

It is a bash script!
I think the binary is in /usr/lib/iridium-browser/
So, try

Code: Select all

ldd /usr/lib/iridium-browser/iridium-brower

Did it.
Below is the result.

Code: Select all

root# ldd /usr/lib/iridium-browser/iridium-browser
	linux-vdso.so.1 =>  (0x00007fff7b9f2000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fab409a8000)
	libffmpeg.so => /usr/lib/iridium-browser/./libffmpeg.so (0x00007fab4053e000)
	libatomic.so.1 => /usr/lib64/libatomic.so.1 (0x00007fab40336000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007fab40132000)
	librt.so.1 => /lib64/librt.so.1 (0x00007fab3ff2a000)
	libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fab3fbf0000)
	libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007fab3f9ee000)
	libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fab3f7cc000)
	libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007fab3f5c9000)
	libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007fab3f3bf000)
	libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007fab3f1bc000)
	libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fab3efaa000)
	libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007fab3eda4000)
	libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007fab3eb94000)
	libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fab3e98a000)
	libXtst.so.6 => /usr/lib64/libXtst.so.6 (0x00007fab3e784000)
	libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007fab3e531000)
	libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fab3e220000)
	libnss3.so => /usr/lib64/libnss3.so (0x00007fab3ded9000)
	libnssutil3.so => /usr/lib64/libnssutil3.so (0x00007fab3dcac000)
	libsmime3.so => /usr/lib64/libsmime3.so (0x00007fab3da80000)
	libnspr4.so => /usr/lib64/libnspr4.so (0x00007fab3d841000)
	libcups.so.2 => /usr/lib64/libcups.so.2 (0x00007fab3d5c1000)
	libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007fab3d239000)
	libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fab3d010000)
	libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fab3cdcd000)
	libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007fab3cb81000)
	libXss.so.1 => /usr/lib64/libXss.so.1 (0x00007fab3c97d000)
	libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007fab3c772000)
	libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007fab3c54d000)
	libatk-bridge-2.0.so.0 => /usr/lib64/libatk-bridge-2.0.so.0 (0x00007fab3c31e000)
	libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007fab3c111000)
	libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007fab3bec5000)
	libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007fab3bbb1000)
	libasound.so.2 => /usr/lib64/libasound.so.2 (0x00007fab3b8b1000)
	libm.so.6 => /lib64/libm.so.6 (0x00007fab3b5a8000)
	libgtk-3.so.0 => /usr/lib64/libgtk-3.so.0 (0x00007fab3ac79000)
	libgdk-3.so.0 => /usr/lib64/libgdk-3.so.0 (0x00007fab3a99e000)
	libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007fab3a77c000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fab3a3fa000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fab3a1e4000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fab39e1a000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fab49db3000)
	libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fab39c16000)
	libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007fab39a10000)
	libffi.so.6 => /usr/lib64/libffi.so.6 (0x00007fab39808000)
	libpcre.so.3 => /lib64/libpcre.so.3 (0x00007fab39598000)
	libplc4.so => /usr/lib64/libplc4.so (0x00007fab39393000)
	libplds4.so => /usr/lib64/libplds4.so (0x00007fab3918f000)
	libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007fab38f45000)
	libgnutls.so.30 => /usr/lib64/libgnutls.so.30 (0x00007fab38c15000)
	libavahi-common.so.3 => /usr/lib64/libavahi-common.so.3 (0x00007fab38a09000)
	libavahi-client.so.3 => /usr/lib64/libavahi-client.so.3 (0x00007fab387f8000)
	libz.so.1 => /lib64/libz.so.1 (0x00007fab385de000)
	libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007fab383da000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fab381b8000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fab37f9d000)
	libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fab37cf3000)
	libsystemd.so.0 => /lib64/libsystemd.so.0 (0x00007fab49f3d000)
	libatspi.so.0 => /usr/lib64/libatspi.so.0 (0x00007fab37ac4000)
	libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007fab378ae000)
	libthai.so.0 => /usr/lib64/libthai.so.0 (0x00007fab376a5000)
	libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007fab373fd000)
	libpng12.so.0 => /lib64/libpng12.so.0 (0x00007fab371d8000)
	libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007fab36fd4000)
	libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007fab36dca000)
	libcairo-gobject.so.2 => /usr/lib64/libcairo-gobject.so.2 (0x00007fab36bc1000)
	libepoxy.so.0 => /usr/lib64/libepoxy.so.0 (0x00007fab368cc000)
	libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007fab366c9000)
	libxkbcommon.so.0 => /usr/lib64/libxkbcommon.so.0 (0x00007fab3648a000)
	libwayland-cursor.so.0 => /usr/lib64/libwayland-cursor.so.0 (0x00007fab36282000)
	libwayland-egl.so.1 => /usr/lib64/libwayland-egl.so.1 (0x00007fab36080000)
	libwayland-client.so.0 => /usr/lib64/libwayland-client.so.0 (0x00007fab35e71000)
	libmirclient.so.9 => /usr/lib64/libmirclient.so.9 (0x00007fab35bca000)
	libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007fab358f8000)
	libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007fab356c9000)
	libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fab354c5000)
	libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007fab352ba000)
	libp11-kit.so.0 => /usr/lib64/libp11-kit.so.0 (0x00007fab35056000)
	libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007fab34e23000)
	libtasn1.so.6 => /usr/lib64/libtasn1.so.6 (0x00007fab34c10000)
	libnettle.so.6 => /usr/lib64/libnettle.so.6 (0x00007fab349da000)
	libhogweed.so.4 => /usr/lib64/libhogweed.so.4 (0x00007fab347a7000)
	libgmp.so.10 => /usr/lib64/libgmp.so.10 (0x00007fab34527000)
	liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fab34305000)
	libgcrypt.so.20 => /lib64/libgcrypt.so.20 (0x00007fab34024000)
	libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007fab33dc6000)
	libdatrie.so.1 => /usr/lib64/libdatrie.so.1 (0x00007fab33bbe000)
	libmircommon.so.7 => /usr/lib64/libmircommon.so.7 (0x00007fab33977000)
	libmirprotobuf.so.3 => /usr/lib64/libmirprotobuf.so.3 (0x00007fab33705000)
	libcapnp-0.5.3.so => /usr/lib64/libcapnp-0.5.3.so (0x00007fab3347d000)
	libmircore.so.1 => /usr/lib64/libmircore.so.1 (0x00007fab33274000)
	libboost_system.so.1.58.0 => /usr/lib64/libboost_system.so.1.58.0 (0x00007fab33070000)
	libprotobuf-lite.so.9 => /usr/lib64/libprotobuf-lite.so.9 (0x00007fab32e3f000)
	libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fab32c3b000)
	libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007fab32a27000)
	libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007fab32801000)
	libboost_filesystem.so.1.58.0 => /usr/lib64/libboost_filesystem.so.1.58.0 (0x00007fab325e9000)
	libkj-0.5.3.so => /usr/lib64/libkj-0.5.3.so (0x00007fab323c0000)

[Mike Walsh]

@ d_vineet:-

Sorry to be a while getting back to you. Family 'stuff', I'm afraid; real life's always getting in the way of the Forum!

As promised, here's a MenuEntry .pet for Iridium. If you've installed it from the .deb package, this will definitely work; it does for me.

You'll find it attached to the bottom of this post. I'll do this for you this once; I don't mind doing that. What I suggest you do is to extract the contents of the MenuEntry, and study the structure. If you ever need to make your own in future, just substitute the appropriate bits for whatever package you're making it for. Icons can be found quite easily by doing a Google or DuckDuckGo search for 'PNG icons for xxxxxx'. PNG have a transparent overlay, and look a lot more professional on the desktop.

Once you have your contents inside a suitably-named directory, simply go into the terminal and create a .pet package with the 'dir2pet' command. Others can explain all about this nearer the time if you need help with it.

BTW, that read-out from your last post looks A-OK to me. All dependencies are satisfied; nothing is listed as missing. It's exactly what you would expect to see from running

Code: Select all

ldd

...on a working package.


Mike.

[d_vineet]

@Mike Walsh,
Thank you very much for your detailed reply and .pet file.
It was initially not working.
When I double-clicked it, Xarchiver could not open it.
Tried to install through dpkg -i <filename>.
But my dpkg seems to be broken.

Code: Select all

dpkg: error: failed to open package info file '/var/lib/dpkg/status' for reading: No such file or directory

Then I fiddled with reinstalling dpkg through PPM. But same issue.
All folders within dpkg are blank.

But now when I double-clicked it, the same .pet file got installed through PPM.
There is now a menu item for iridium and it works.
Don't know what happened.

I will try to prepare a different .pet for another program and learn more about pet files.

Thanks again.

[foxpup]

dpkg is not something in Puppy. It will not work properly in Puppy.
Puppy has its own package manager: PPM Puppy Package Manager. Clicking a .pet file should have the pet-package installed by PPM.
I don't know why it did not work in the first place.
BTW, I think dpkg is in the Dogs It is even the preferred package manager in the Dogs.
You should know there are Puppy-like Dogs , builds that look like Puppy but are more like the big distro they are based upon (debian, ubuntu ... ).
You will find threads about them in this forum. In time try them out and see if you like them.
BTW, you know that most Puppies (and Dogs) are based on a big distro?

To extract, not to install, a pet you better use Uextract. It is a very usefull swiss knife tool, but not installed in all Puppies.
If it is not in your Puppy (look in the menu or in /usr/share/applications/ ) you can install it with a pet. Google for it to find the topic with download link in this forum.

I will explain a little more about the menu-entries. Otherwise I find it hard to understand what Mike is saying, if I may Mike.
To be in the Menu, there has to be a .desktop file in /usr/share/applications/
You can look there for examples. You can open .destop files as text.
There has to be some lines in it: Exec, Icon, Categories... It can be quite elaborate.
The Categories line determines where the entry will come in the structure of the Menu.