PPM: incorrect deps for pppoeconf

In the Puppy package database, the deps for package 'pppoeconf' are shown as:


However the original information is this:

Depends: whiptail-provider | whiptail, ppp (>= 2.4.2+20040428-2) | pppoe (>= 3.0), ppp (>= 2.4.1.uus2-4), gettext-base (>= 0.13), sed (>= 3.95)

The simplification done by the '0setup' script has been inadequate in this case. I already reported that when I clicked the "Examine dependencies" button for the 'pppoeconf' package, it just exited to the main GUI window. I checked at packages.ubuntu.com and there is no package named 'whiptail-provider', not for any version of Ubuntu. Perhaps its an old Debian package.

There are two ways to solve this problem:

In woof/PKGS_MANAGEMENT, and also in a running Puppy in /root/.packages/PKGS_MANAGEMENT, there's a variable:

#alternate names of a package (used in filterpkgs.sh)...
PKG_NAME_ALIASES='mp,mped rxvt-unicode,urxvt cxxlibs,glibc*,libc* alsalib,alsa-lib libungif,libgif zip,infozip dbus,libdbus*,libdbus-glib* hal,libhal* xorg_base,xorg_base_t2,x11-common,x-dev,xorg acl,libacl* xdg_puppy,xdg-utils'

The original intention of this variable was for the situation where PET packages may have slightly different names than the same ones in a compatible-distro. This variable will prevent a package from being listed in PPM in a cmpatible-distro databse if in fact it is an already installed PET package.

Note it also accepts glob wildcards.

This variable is used in scripts findmissingpkgs.sh, filterpkgs.sh, dependencies.sh (in /usr/local/petget), all part of PPM.

I could add "whiptail,whiptail-provider".

2. Fix 0setup
I will have to ask John Doe about this, as he has recently rewritten '0setup' to be much faster at converting the compat-distro databases into the simplified Puppy format.

A question would be, how difficult would it be to check if 'whiptail-provider' actually exists in any of the Ubuntu repos, then if not choose the alternative?
I can see that it could be done, but it would slow the conversion way down perhaps.

A fundamental problem is, 0setup always chooses the first choice, on the left of the '|', which seems to work mostly, but not always.

I was planning to enhance the deps field, may have to bring that forward. We could simply preserve the '|' except use a different symbol. I also want to allow for specifying a particular version when it is absolutely required, but not use the '<' or '>' characters. Maybe something like:


...meaning greater-than-or-equal-to, equal-to, and less-than-or-equal-to.

Posted on 23 Apr 2009, 17:02


Posted on 23 Apr 2009, 24:25 by John Doe
The deps field was one I was going to clarify with you. One of the things I forgot was to add logic for it in the arch script.

I'm heading out the door right now though. First sunny day this week.

I'll write up some lengthy correspondence tonight and get working it out later tonight here. Should be about mid-day tomorrow for you over there.

Posted on 24 Apr 2009, 8:23 by Leon
rp-pppoe fixed

Thank you for fixing pppoe and solved many other problems as well.

Jaunty Puppy 4.6.3 works fast and well for me.

Short Test Report

System informations
Frugal install, Intel P4 1,7GHz, 1GB Ram, 80GB IBM ATA IC35L080AVVA07-0, NEC DVD_RW ND-2500A, TEAC CD-W552E, Ati Radeon 9200 SE graphic card, Sony SDM-M51 15" LCD monitor

Mouse and keyboard: OK

Graphics: Xorgwizard offers only 640x480 resolution but after manually modified /etc/X11/xorg.conf file 1024x768 resolution is enabled.
Excellent font rendering when DejaVu Sans 12 font is replaced with Helvetica in both GTK and Jwm themes.

Sound: ICH-Intel 82801BA-ICH2 Audio AdapterProperly detected and enabled
Problem: Settings not saved after reboot

Printing: OK
Printer Driver: HP LaserJet 4P - CUPS+Gutenprint v5.2.3 Simplified
Device URI: parallel:/dev/lp0

Internet connection: OK
I'm writing this from Jaunty Puppy 4.6.3 and both rp-pppoe - eth0, Ethernet via-rhine, pci: VIA Technologies, VT6105/VT610S Rhine-III - ADSL and PupDial - Manhattan USB Modem - analogue phone line Internet connections works fine.

Locale: sl_SI settings properly set and saved

Jwm windows manager: Works
Problem: No menu icons

Posted on 24 Apr 2009, 10:37 by BarryK
Re: no menu icons
This report of no menu icons for JWM puzzles me. You are not the only one reporting it.

I have only tested Jaunty 463 on three computers so far, and do get the icons ok.

The only issue I had was with Rox on the Ntavo thinstation, where got a black desktop (but JWM and menu icons were ok).

Posted on 24 Apr 2009, 10:40 by BarryK
Re: fast 0setup
I got around to looking at your 0setup last night.

Um, yes, fields missing in the Ubuntu case.

The point of the exercise is that all compat distros must generate the same standard database format, and all fields must be present and in the same order.

Posted on 24 Apr 2009, 16:24 by John Doe
Re: Re: fast 0setup
understood. thanks for the reminder.

upon review of my comments, I recall some confusion regarding column count vs column output. the method is still sound. I'll fix it up over the next couple days.being

Posted on 28 Apr 2009, 8:10 by Leon
Missing menu icons
I never saw this problem before.
When I switched from Xorg to Xvesa all icons reappeared.

The other main problem is Alsa settings that are not saved at reboot.

Other basic features works surprisingly well for me.