Hello, I have a really ludicrous idea about a puppy derivative. I need to know, how can I get the current code in the woof build system into the original pUPnGo. Also how to a compile a glibc from scratch?_________________....

while having a big online repo and having some unity no matter what modules you have loaded. I want this to be distro that will benefit all (whether want to use on a P3 system, Atom netbook, or on some thousand core gaming system), there will be something for everyone._________________....

In order to ever make that work I imagine you would have to have a very tightly written set of definitions and parameters that different people could work to. And then lots of testing, bug fixing, and rewriting of the definitions and parameters..

It is possible, not too difficult and has been done (mostly via zdrv.sfs), but dont expect all apps from other distros to work with other kernel versions, they dont all build packages against a lowest common denominator ... Fyi If you build packages against Linux 2.32, glibc-2.6ish and gtk2.12 (and corresponding dependencies) they are pretty likely to work on other distros... Basically build against the oldest version that will build it if you can. There are other considerations like stack smashing, etc... Someone really should post a portability howto wiki somewhere for other builders._________________Check out my github repositories. I may eventually get around to updating my blogspot.

Hello, I have a really ludicrous idea about a puppy derivative. I need to know, how can I get the current code in the woof build system into the original pUPnGo. Also how to a compile a glibc from scratch?

I have not tried any of the two so cant advise here. You are sure pupngo is a healthy starting point? (I'm not)...
Maybe Debian or some other large distro already close to target?

Here is the low down. Since pupngo's multicall binaries were statically built against a kernel older than any major distro uses, they can be used with all of them.

Now, some stuff (not much) will need to use the distro version like squash tools where newer versions are now in the vanilla kernel and stable but were only patches in the older kernels and are incompatible._________________Check out my github repositories. I may eventually get around to updating my blogspot.

Here is the low down. Since pupngo's multicall binaries were statically built against a kernel older than any major distro uses, they can be used with all of them.

Now, some stuff (not much) will need to use the distro version like squash tools where newer versions are now in the vanilla kernel and stable but were only patches in the older kernels and are incompatible.

Oh, I wondered why you where doing so muchwork to a very old base, I kept waiting for something newer... Now it makes sense, except that I do not see any newer roll outs, are they being uploaded somewhere?

Ted Dog: The possibilities for posting new variants of pupngo are huge but for the moment my ideas for posting other than what would be considered remasters are not present.
Other developers much more skilled than I deliver small basis with package managers to build up custom systems. Atm the static linked principle seems the most unique pupngo feature still not handled by most other puplets. So I cruise around, collect apps that potentially add functionality/variability to a possible future pupngo - but at the same time can be used today in a broad range of puppy versions (and beyond..).

They were done in Windows running pupngo in vmware - I do not recall the name of capture software - sorry. Hopefully same quality can eventually be done with xvidcap but I haven't been able yet to do that.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum