Scott J

Rather than SDL, maybe something like these "single header" and/or "ANSI C" GUI libraries might be easier to use: - https://github.com/vurtun/nuklear - https://github.com/nakst/luigi - https://github.com/floooh/sokol (not a single library, but...

I think I have encountered this issue when using Pkg too - trying to find which package a file comes from is made tricker in these cases, if the package...

Puppy version: FossaPup64 9.5 I was trying to find out which package the `/usr/sbin/puppyapps` script comes from: - it is not listed as an installed package (built-in)  I tracked...

I've banged on about the need for a proper Developer Handbook, lots.. Hopefully it'll go somewhere.. The CRUX Handbooks are simple, and really nice - using lots of small, easy...

Is this because Puppys didn't used to include the ca-cert package that puts cert stuff in /etc/ ? ..cos I think all Puppys have them now, as [something I can't...

I know all this... I'm **not** proposing we add actual man pages into the puppy SFS ... I'm proposing we make the `man` command better at finding the right man...

I like the idea of this... I do like the idea of at least somewhat following the convention of having - "base" packages at `/bin` and `/usr/bin` - user installed...

> There is no need for any changes. I agree with peabee... But for completely different reasons.. > Another problem with SFS modules was PPM and Pkg unable to see...

And speaking of ADRV etc... I'm just gonna put it out there: "adrv", "zdrv", "fdrv"? ....Really?! They should be called something helpful, not cryptic and weird.. Like ``` puppy-9.5.sfs kernel-5.4.33.sfs...

> Clear file representation in todays world helps speed adoptions. Indeed.. Here's some fun facts: - 90% of people leave a webpage after just under 2 seconds of waiting for...