This began as an answer to bigpup's Question which I'll paraphrase "If you don't have a web-browser, how do you get one?"
You don't need a web-browser now that F96 has Quickpet. Quickpet uses the built-in wget. Unfortunately, unlike Bionicpup64's Quickpet, F96's Quickpet doesn't offer any.
- Quickpet Comparisons.png (39.93 KiB) Viewed 1858 times
What is needed is to upload one --and only one-- to the repo Quickpet accesses. [More than one may be nice to have, but isn't necessary and would require additional maintenance of the repo]. I would suggest that the one be built around one of MikeWalsh's portables. Most are updateable relieving even the burden of repo maintenance. Once there's a SaveFile/Folder a portable initially located in /opt can be externalized in two quick steps: (1) drag folder to /mnt/home, select Move; (2) drag folder back to /opt and select Link(relative). All setting and customizations are preserved; updates of browser no longer require a Save to preserve them; and web-cache is re-directed out of RAM.
Pick one. I'll built it and upload it to mediafire. What I can't do is upload it to the repo that Quickpet will access.
[I've seen a notice when attempting to start some application that hadn't yet been installed to use Puppy Package Manager. Something like that --but directing to Quickpet-- could be the 'Default Web-browser' until an actual Web-browser is obtained and set as default. What I can't do is write it].
The existence of Quickpet changes what has to be in either the core/base sfs or provided by an 'alphabet' drive. Why include applications that aren't wanted by some when others who want them can easily install them? Fleshing out Quickpet's repo means less complications in Woof's Recipe, less transmission required by Users, and I suspect less over-all on line storage needed.
Maybe to avoid confusion F-96 needs it own repo? Edit: Maybe not. I've just booted into Fossapup-9.5. Its Quickpet offers web-browsers. Likely, they date from 2020 and IIRC were downloaded as pets to be installed (maybe SFSes). Either way, difficult to update. Maybe all that is necessary is to replace the offering in the repo. FROM experience, there are no web-browsers which will run in F-96 that won't run under fossapup64-9.5.
IIRC, there was mention that using some applications built for fossapup64-9.5 would be problematic under F-96. Which? That hasn't been my experience. But if so, the easy solution is to replace those on the repo. I don't know of any application built for F-96 which won't run under fossapup64-9.5. [Maybe a 'legacy' repo is needed into which deprecated applications can be moved].
Greater use of Quickpet solves most of the issues fr-ke raised here, https://www.forum.puppylinux.com/viewto ... 237#p77237. But it would also solve a problem I encountered. I never use Conky. If and when I want that information I can easily get it. But unless I remove Conky it just creates what I consider a displeasing cluttering on my desktop which interferes with the display by pwidgets that I do want. I used to be able to just remove it from Autostart. But under F-96 I've discovered that while that works when using a SaveFile/Folder if the latter is converted to an adrv/ydrv, Conky is back. [I think files in /etc re-install it to Startup]. Conky has been placed in ydrv. To get rid of Conky I have to mount and rebuilt ydrv removing it from both /etc and Startup. Why do I have to spend a half-hour removing something I didn't want in the first place.
Conky isn't like other applications whose display can be turned off with Menu>Setup>Menu Manager.
@ fr-ke: Removing builtin Applications is mostly a waste of your time. See, viewtopic.php?t=692&sid=5e6deb390a84c48 ... 3174eadfb1. It makes far more sense to just turn off annoying Menu entries.
@ radky, Menu Manager is one of the important applications to have available when you are initially customizing a Puppy. For some reason, its application desktop file includes the argument NoDisplay=true so it doesn't appear on the Menu. Newbies won't know its available. Unless they know of its existence, know to edit /usr/share/applications/menumanager.desktop they'll have to start JWMDesk and click the Menu tab; and they probably won't know to do that either. It may be that once a user is satisfied with customizations then Menu Manager will rarely be needed and it can be used to 'turn itself off'. But until then IMHO it should be 'in your face' available.
radky you build great applications. I've frequently recommended them. I've even argued that a newbie friendly Puppy with a modern appearance should have both JWMDesk and PupControl with all the other menu entries to applications accessible thru JWMDesk and PupControl not displayed on the menu rather than the 'old-style' with menu entries for all applications. But what we now have is both, and an even more cluttered and confusing menu.
We are no longer rushing to meet some DistroWatch deadline. Thanks primarily to radky's and rockedges' hard work* at this stage we have a Fossapup which has greater potential than many of us envisioned when we started. I recommend that we take the time so that when it is published it will be the best we can offer: newbie friendly -- easy to use, easily customizable, and easy for both devs and users to maintain.
* and an occasionally, when needed, assist from dimkr and others