It shouldn't be too hard to achieve - we just need many static binaries.
I was able to replace init, syslogd, etc' from BusyBox with lazy-utils, udev with devd, Bash with loksh, etc' in Slacko and achieved an identical-looking Puppy, that uses less RAM and boots faster. It's easy to build static versions of these, so it shouldn't be very hard to make a "common" repository for x86_64.
I'm currently focusing my efforts on a small Xfbdev and a basic desktop that runs on top of it - once everything is ready, I'll try to make woof-CE capable of building a 64-bit, "mini-Puppy" with all these small alternatives.
EDIT: by the way, why don't we just try to build a 64-bit Slacko (without any applications) right now? We can use the 32-bit static binaries for now.
Iguleder, I'll wait til you've done your next clean up then I'll go for it! And I'll go the whole hog, hacking in 64 bit support. I'll build a kernel in fatdog for now then download and unpack the slackware64-14.0 bins. I can use Fatdog static bins in the initrd for now too. It will be a kind of thinSlacko64..
I notice that t2 v9.0 has both 32 and 64 bit versions of packages as do Opensuse and Mageia, I suspect the others are similar. I had been considering a 64bit for the extra abilities it gave with the ability to have concurrent multi-desktops and servers...
I was wondering if...
woof-arch had a x86_64 branch containing the basic 64bit stuff (most of it seems common between distributions, just rebuilt for theirs) so ?maybe just assembling/building puppy versions would work here? as well as our puppy 'special scripts'. ?Iguleder, does this seem right as I have only had a quick look through my distros so far.
woof-code had the ability to deal with both 32 and 64bit --A LOT OF CHECKING AND RE-WORK I think
woof-distro had a x86_64 branch containing the various sources and their x86_64 bit package equivalents to the 32bit packages.
That way we could remain true to the woof system layout.
I have been tracking down sources and compiling static binaries and stealing others from slackware and fatdog. Built a kernel too. I should have the inaugural woof-CE 64 build booting by the end of January.
Hah! I have it booting to a broken desktop! Never mind the desktop is broken.. system works!
Posting from it now. .. bit like a drunken desktop.. :P
Still.. Xchat is working, Firefox is working, net connected ootb, desktop is all the triangles and grey BUT the jwm menu is working with all icons.. so it's weird, well, not weird, it's rox! And rox can be weird!
Here is a teaser! I have fixed the desktop and compiled some basic stuff, mtpaint, geany; fixed a heap of bugs also.
Immediately on the TODo list:
*recompile kernel (current one is built in slackware64-14.1, I only support 14.0 for now, different gcc, so drivers may not build)
*allow it to build itself in woof, that should be doable now. I had been using FatDog, but glibc is too old and depmod fails in woof. Currently building in slacko 32 bit.
*build some more basics --tray icons, osmo, later on abiword and gnumeric
I'll announce it here, not on murga because it's not ready for consumption yet. It's basically ready to build on. I have new2dir working and have been compiling, geany, fltk>flsynclient, sylpheed, a heap of the small puppy specific utils, .pupevent*, >elspci, >truncate and other stuffs.
Still need to do the static *mm (gtkmm and friends) to build gparted, then goffice >gnumeric,abiword, then some codecs and dvd utils > ffmpeg.. and plenty more!