Distributions created by Forum members

[s243a]

EDIT2: The reason I mentioned Void Linux, and why I'm myself currently interested in it, is that it does have its own independent package manager/compiling build system called XBPS I think. So if void repos were small and good enough that could be used on top of a tiny Puppy boot system. The result would not be void linux, it would be a puppy but with void linux package management and void packages - not like Tazpup with Slitaz, which only starts as Puppy but really drives normal Slitaz once it gets going (I do like Tazpup a lot though, it's normal slitaz but with Puppy save options etc, which is a huge bonus). No, this would be more like BionicPup say, but with void repos and using void package manager rather than modifed pkg or petget to fetch the desired void packages.

wiak

x-slacko slim seems to support installing void linux packages. Maybe for this reason it would be a good choice of puppies to create a stripped down version. I created a new thread about stripping down a puppy.

[wiak]

I created a new thread about stripping down a puppy.

Yes, that's good initiative. Clearly a lot of potential contributors are interested in that, so a dedicated development thread for that purpose should help. The result wouldn't be a woof-CE built pup probably but at the end of the day I doubt users really care how a distro is created - a great distro is a great distro and where to find info and download for such is what most people really want to know.

wiak

[wiak]

x-slacko slim seems to support installing void linux packages. Maybe for this reason it would be a good choice of puppies to create a stripped down version.

Hmmm, that's a very interesting pup (I'm downloading it now) - mistfire is (and has been) doing some really great work on this forum, though newcomers probably don't know much about that.

However, though it says in the X-slacko-slim description it has support for various linux repos (including void packages) I doubt (?) that includes full dependency resolution, which is really the crux of the matter, and would need special package manager support (hence my mentioning void's package manager XPBS itself). Still, X-slacko-slim, or something similar would be a good start.

[wanderer]

hi wiak

are you going to do a woof-ce minimal pup

based on x-slacko slim

just asking

wanderer

[mistfire]

@wiak thank you for recognizing TazPuppy.

About multi-package format support in X-Slacko Slim it supposed to work the same as PPM when it comes to package dependency resolving.

[wiak]

@wiak thank you for recognizing TazPuppy.

About multi-package format support in X-Slacko Slim it supposed to work the same as PPM when it comes to package dependency resolving.

TazPuppy is definitely one of the distributions developed on Puppy Forum that is leading the way in terms of innovation and possible ways forward for Puppy itself more generally IMO.

Regarding X-Slacko Slim saying it can install from void linux repositories - surely that does not include the ability that it does any dependency resolution for void packages? I can understand that PPM has been written to make best effort attempt to resolve dependencies for Debian/Ubuntu/Slackware maybe, but I feel it is unlikely to do the same for void.

So I would guess it can install and individual void package but up the the user to work out and install the dependencies manually for void case?

I also imagine that would also be a limitation in sc0ttman's pkg program (if that were added to X-Slacko Slim) when it comes to trying to install packages from void linux repos??

wiak

[darry19662018]

Void would be a great base for a Puppy though:)

[wiak]

hi wiak

are you going to do a woof-ce minimal pup

based on x-slacko slim

just asking

wanderer

No wanderer, personally I have given up working with woof-CE; I had no direct access rights to that anyway, which is one reason I ended up creating makepup, so I could semi-automate woof-CE builds without having to have my code continually checked and accepted or not accepted by woof-CE 'gatekeepers'.

Also, given a complicated to make recipe, woof-CE then just repeatably spews out the same iso (well, okay, you can modify config script to not include a few packages, but nothing major easy really) - I don't really see the point of rebuilding same iso after so much work adding new recipe - that's not very flexible (no user choices of Desktop Manager etc, so many questions to answer when building via woof-CE scripts - no simple config to allow a fully unattended build via commandline script, but little point anyway if much the same iso built each time IMO. It's a recipe for building these kind of pups, so good for that history at least.

Having thus given up entirely on woof-CE-related development I have also asked someone I noticed was using makepup if they would take over its maintenance and development, which they have agreed to. I believe their plan is to merge makepup into woof-CE itself, which would certainly help with makepup's maintenance since changes in woof-CE can break makepup itself (and do).

I'm still interested in 'Puppy' though, or at least in what a future Pup-type system would be like. My view of woof-CE is that it managed to do its original design job, which was to allow 'recipes' for building a Pup from a few upstream distro repos - though mainly only Debian-based and Slackware.

My interest in X-Slacko Slim, aside from it looking like a nice piece of remastering work, was mainly because it claims to be able to handle packages from a considerable number of upstream repos (including void) but I suspect that does not include the pky manager dependency resolution mechanisms which are really needed overall.

I find TazPuppy much more interesting and innovative really though, and more so than any new recipe added to woof-CE for one-off Pup iso builds (we already have the Dogs doing already perfect Debian/Ubuntu puppy-sized with full puppy-like functionality and more, afterall; frugal install, root user, sfs handling and so on).
Funny how someone questioned why I included TazPuppy in my first post list of distros being developed on this forum - the reason is simple: it is innovative and thus important for Pup future. CorePup is more straightforward since really just puppified TinyCoreLinux, but thats a good illustration/exemplar of what is needed for any pup build system: flexibility, modularity, user-selectable choice etc.

wiak

[wiak]

Void would be a great base for a Puppy though:)

Very good base I feel. Its weakness is mainly just lack of documentation and too many contradictions in its provided wiki documentation. I know; I've been working on installing it. It's package manager seems 'great!' - very much like using apt in Debian, but completely independent written by void team. The way packages are separated means has flexibility required to allow building of very small distros using them. Yes, a great base for Puppy - just need build scripts produced like mistfire does for TazPuppy - which should be commandline driven to allow user-config-customisable unattended builds (such mechanism also makes optional GUI easy).

Certainly means Puppies built that way won't be independent themselves since relying on upstream Void repos, but woof-CE Pups are entirely not independent creations nowadays anyway - the rely on huge Debian/Slackware for their main functionality. At least Void allows compiling of void packages and the compiles in void repo are specially made and modular - and, yes, no systemd in Void itself (nor the somewhat messy old sysVinit) - well worth adopting 'runit' as used in Void instead - its service start/stop mechanisms is simple and flexible (using sv start/stop/restart service_name etc). EasyOS is a different kettle of fish: it borrows a lot from Puppy, but is innovative and doesn't depend on Debian/Slackware as far as I understand it - independent and new.

wiak

[wanderer]

i note there is on the forum

a myriad

of puppy inspired projects


i just tried dpup

a beautiful piece of work


wanderer

[wanderer]

hi all

i am posting this from puppy 8 32 bit

light browser

everything is working great

looks very awesome


wanderer

[musher0]

Hello all.

If anyone feels creative, in this post you will find a way to access a not-so-old
woof-CE-Testing archive enabling you to create a wide range of Puppies. Please go
and see, the list is rather long, and it would not be appropriate to repeat it.

Unfortunately, Woof-CE is not offering creative Puppyists such a wide choice of builds
anymore, AFAIK. Hopefully, some of you will be the next generation of Puppy-builders!

Enjoy!

[wanderer]

hi all

just posting

i am now using bionicpup32
and it is working great

its great to be back using a puppy again
i had forgotten a lot

i stopped using puppy
because i couldn't get any of the new puppies to work

then i started playing with corepup

maybe i will eventually woof-ce a puppy after all

i will also continue to play with corepup of course
since that is also a great system

will post again soon

wanderer

[fredx181]

hi wanderer,

i will also continue to play with corepup of course
since that is also a great system

Sure, corepup can become great, but I think you should try getting some help from puppy developers to make it being more like a Puppy, by maybe e.g. including programs adopted from Puppy, if possible, support for .pet packages etc...
Working on it alone is... just alone, not very stimulating IMHO.

Fred

[wanderer]

thank you fredx

yes i need help

i need to know how to change puppy sfs files and pets

into ordinary folders

than i can either symlink the folder to root

or make them into a tcz

also i need to look at the deb2tcz script


im working on it but slowly and inexpertly as usual


thanks for the encouragement


wanderer

[mikeslr]

thank you fredx

yes i need help

i need to know how to change puppy sfs files and pets

into ordinary folders

than i can either symlink the folder to root

or make them into a tcz

also i need to look at the deb2tcz script

Hi Wanderer,

ITMERSH's PaDS 1.1.4, http://murga-linux.com/puppy/viewtopic. ... 922#998922 can already make use of .tazpkg's as well as other containers in the creation of SFSes and Pets. During the creation process it decompresses the 'source' container into a folder. However, that folder ceases to exist when the pet or sfs has been created.

Perhaps, if asked nicely, ITSMERSH could either modify PaDS or make a special version for use with Corepup to (a) either generate a tcz or (b) leave the 'Work-folder' in existence.

(b) Would be easier: merely copy the 'Work Folder' before compression. (a) would require knowing differences, if any, between how puppy structures and uses files; and, if nothing else, any special requirements pertaining to generating menu-listings. [By way of illustration, debs created for debian or Ubuntu often use "Category" definitions not employed by Puppies].

[wanderer]

thanks mikslr

sounds great

i will check into it
maybe i can stop the script before it deletes the folder

wanderer

[wanderer]

i am checking it now

he has done fantastic work

wanderer

[mikeslr]

It's been a while since I examined PaDS carefully; and coding isn't my 'strong-suit'. But, I know there's a point just before a pet or SFS is created where User input takes place: such as to select among multiple icons for the menu - or just press "Finish". Shouldn't be difficult to include a 'copy folder to somewhere' command just after that, before compression occurs.

Even more comprehensive would be SFS's UExtract which can decompress pets, and tcz's among scores of containers, creating a folder within which are a copy of all the files from the container organized according to the structures they had in the container.

[wanderer]

thanks mikeslr

looks like just what i need


wanderer