how many distros does woof-ce support?

[wanderer]

i was just wondering

how many distros does woof-ce currently support
ubuntu slackware

i was reading an article that lists puppy as one of the best distros for development
but it only lists ubuntu and another one i forget
i will try to find the article again

i also read an article that lists puppy as the go to "small distro"

so thats cool

wanderer

[darry19662018]

Hi Wanders,
Support is for Debian, Slackware and Slackware and Archpup.

T2, and Devuan (A point of much annoyance by me) were dropped.

[wanderer]

thanks darry

wanderer

[bigpup]

Support is not really a good way to look at it.
It is where does Puppy get the core Linux files and programs, used to make it a Linux OS?
All Linux OS's need and use these same files.
Puppy Linux does not have a repository of all Linux files and programs.
So Puppy Linux gets them, from other Linux OS's, that do have well kept repositories.

From Woof-CE

Choose a compatible-distro.
This is the distro whose packages you are going to 'borrow' to build your Puppy.
Open file DISTRO_SPECS in a text editor and change this line:
DISTRO_BINARY_COMPAT="ubuntu"
to what you want: 'slackware', 'devuan', 'ubuntu', 'debian' or 'puppy'.

The accessed repository(distro), of other Linux OS's, is fluid and can be added to or deleted from.

[wanderer]

so there is a puppy core - core packages init system skeleton etc

and woof-ce can download and convert to be compatible with the puppy core
packages from other distros

and then build the puppy iso

but they have to be able to be made compatible
if they are too different in structure they will not work

so there are some limits to the particular distro repositories that can be used

right ?

wanderer

[peebee]

3 (or 8.5) - Slackware (14.0, 14.1 & 14.2), Debian (Buster & Stretch) and Ubuntu (Trusty, Xenial & Bionic) + Ubuntu Focal64

see: https://github.com/puppylinux-woof-CE/w ... distro/x86

Other distros can be used but have to be crafted by the dev (e.g. Slackware Current, ArchLinux, Devuan)

[wanderer]

thanks guys

great work

much appreciated



wanderer

[mistfire]

I just wondered, why there is no support for creating puppy from Fedora packages?

[peebee]

I just wondered, why there is no support for creating puppy from Fedora packages?

Because nobody has created the conversion / translator from the Fedora repo package database format to the internal standardised Woof-CE format - this is the 1st step (in 0setup) in any Woof-CE build.

+ I would guess that nobody has seen sufficient extra/unique apps or features provided by Fedora that are not provided by the existing set of Debian / Ubuntu / Slackware to justify the development of a Fedora -> Woof-CE translator.

Is the Fedora package database format similar to any other?? How easy would it be to develop a translator?

p.s. there are legacy builds maintained on GitHub for other distros that can be used as clues:
https://github.com/puppylinux-woof-CE/w ... distro/x86

[dimkr]

I just wondered, why there is no support for creating puppy from Fedora packages?

Fedora changes often, and a Puppy based on Fedora packages would have short shelf life, a small selection of packages and bad support for third-party packages (stuff like Chrome and Steam).

Adding Fedora support to woof-CE is not super hard, but I don't think it's a useful feature. (I think the same about Slackware Current based builds, builds that use non-LTS Ubuntu packages, and builds that mix and match packages from different distros, to the point they're incompatible with either of these).

[Grey]

Ubuntu is the best choice for a baseline (internals, not externals). Fedora is one of the most awkward options.

[peebee]

I think the same about Slackware Current based builds, builds that use non-LTS Ubuntu packages, and builds that mix and match packages from different distros

????????????? the only build that is maintained within Woof-CE that meets those criteria is build-x86***-slackware-15.0 i.e. Slacko-8 ????????????

[dimkr]

????????????? the only build that is maintained within Woof-CE that meets those criteria is build-x86***-slackware-15.0 i.e. Slacko-8 ????????????

How?

Slackware releases are supported with security and stability updates for a very long time (like Ubuntu LTS releases), don't have breaking changes like Slackware Current, and Slacko is built from mostly Slackware packages, and PET packages built under Slacko (as opposed to, packages borrowed from Debian, or packages built under Ubuntu-based Puppy).

[peebee]

How?

Slackware-15 has not been released (yet) so Slacko-8 is using Slackware Current (ATM) ............ this is presumably acceptable ..........

[dimkr]

Slackware Current is stabilizing - the 15.0 release candidate is already out. This is temporary. After the release, Slacko 8.x will use the 15.0 repo.

[peebee]

This is going OT ........... however if you look at:
http://ftp.slackware.com/pub/slackware/ ... ngeLog.txt

the Slackware-15.0 "Release Candidate" was mentioned on Mon Aug 16 at line 3167 - i.e. there have been >3000 changes (some very major and significant) subsequently .....

There is no sign of Slackware-15.0 repos at:
http://ftp.slackware.com/pub/slackware/

[dimkr]

Waiting for the 15.0 release is not an option - it takes time to create a polished Puppy release.

If you wait for Fedora release x, by the time you achieve a beta quality Puppy that uses its packages, x+1 will be out already, and third party applications like Chrome won't support it anymore.