Possible bug in petget/0setup:
I'm using a pretty bog standard Slacko 6.9.x build..
I'm trying to get Slacko to install wpa_supplicant 2.6, which has fixes against a big security problem in wifi (as far as I understand it)...
This wpa_supplicant 2.6 is in the Slackware patches repo.
The 0setup script, used in Woof and Petget, merges the latest pkgs from the "Slackware patches" into
the main *-official repo files, when updating/building Puppys repo files... (as I understand it)..
That's pretty cool, hat's off
![Smile :)](./images/smilies/icon_smile.gif)
However, while Petget successfully lists wpa_supplicant 2.6 in the repo after an update, it wrongly shows (ALREADY INSTALLED)..
Cos I actually only have 2.5 installed..
Even worse, trying to install any new pkgs added from the patches repo (and merged into "Packages-slackware14.2-official" in Petget) fails..
It says "missing libraries".. Even if I download them in the browser and ldd them (none missing)..
Anyone else have (or can anyone reproduce) the same problem?
(I'm well aware I don't understand Woof very well, so don't wanna just start logging spurious Github issues, so am asking here if I have this all correct...)
[As a side note, after updating the repos, my own pkg manager was able to download and install the wpa_supplicant 2.6, and the new bash
listed in patches without a problem (had to use the --force option to override existing pkgs]
-----------
A feature request
On a very related note, if there are new pkgs in the repos, I would love Puppy to print to the console (or terminal emulator) on first run of each boot
the names of all the new pkgs in the repos, just like Ubuntu does...
Especially if it's security fixes.. To that end it might NOT be better to merge the patches/fixes/security pkgs into the main repo files...
Ideally puppy would check for new pkgs at boot, and if new pkgs found, booting to X would be delayed i until after i had seen the msg and
chosen to install/ignore/etc.. and then X loads up.. (so, more like apt-get/ubuntu)
(this could actually be achieved with my pkg manager fairly easily, if puppy didn't merge the new pkgs into the main repo files and instead
kept the patches/fixes repos in their own files, like all the other repos..)
And wouldn't it be less code and hackery in woof to simply treat the patches (etc) repos like normal repos - with their own repo files...?
Again, I don't know enough about Woof to do this a 'proper' way (using Petget, root-fs skeleton, etc) ...
...Any thoughts?