I'm needing to build ALL packages from scratch... Is there a common order to do this? or is it just go through the tree marking: pkg1 done, pkg2 failed, pkg3 done... and then just process until all are done?

Why would anyone do such a thing?! Well... I'm trying to install slackware on my PPC G4 machine... Slackintosh 12.1 is a bit old and I couldn't get that CD to boot. I installed an old Gentoo PPC version to get the system to boot... I have a second hard drive to install Slackware 13.1/Current onto and then I'll dump the Gentoo drive...

My first thought was to do a LFS tool chain and then begin the packages based on the LFS order but I've already hit snags with dependancies using the SlackBuilds because of old Gentoo and new Slackware. (I'm using sources from 13.1 tree.) -- If i do the LFS configure, the dependancies aren't an issue because it's a temp toolchain.

Or maybe I just need another approach or perhaps my approach is good. Comments, Suggestions or Ideas?

Hey listen...I love Slackware too, but you need to ask yourself if the juice is worth the squeeze.

There is a reason that Slackintosh was created (and indeed, why it died), compiling all of Slackware for a different architecture is no easy task. There is more to it than simply building all the packages for PPC, there are changes and new packages/libraries that need to be added in.

Here is my issue... as it is, the PC is useless... Even the Gentoo I have installed is worthless... So my option is to migrate Slackware to PowerPC or to do a complete BYOL or LFS... No matter what I have a lot of work to do.

Why Slackware? I like the Package management... This is a server so I won't have xwindows or any GUI's which should reduce complexities and reduce the total number of packages... =D

There are other packages that are required and thats fine (like the mac-fdisk and such)

Greetingz!

GrapefruiTgirl had an EPIC thread back in '07 about this very topic.

@Micah

Not that I would attempt to discourage you from such a really cool endevor...but like MS3FGX said, "is the juice is worth the squeeze?"

That's not wholly true, there's a few PowerPC Linux builds out there...or would that be PPC64?

Correct me if I'm wrong, but package-mangement is only handy when you're upgrading/adding/removing software a lot. If you have to compile it all yourself, then the only advantage any sort of package-management software would lend is if you had a large install base of the same type of computer....

Thanks! I'll be reviewing this in depth!

Note 1: It's PPC G4, 32 bit... Custom built Mac (I had to buy refurb/ebay mainboard, cpu and PSU, but everything else is custom.)
Note 2: I've had issues getting ANY linux CD to boot. Gentoo was the first usable, but it's an archaic build and I really don't like Gentoo compared to Slackware (I did use Gentoo for about 3 years, but I still like Slackware better)
Note 3: I have several PCs, 32 bit, 64 bit and a PPC and I like having my custom SlackBuild's that I run and just install - simpler maintenance (yes, it is a hefty up front workload) -- I update some packages alot, but the script remains the same 90% of the time (MySQL, PHP, Apache and such)
Note 4: (more of 3) I'd like to be able to upgrade easily... Most packages will compile using the SlackBuilds without any changes so it'd be nice to just let it recompile it and install it -- like I do on my VIA C7 CPUs (I do a few extra optimizations too).

and Lastly... I need something to do =P

Side Note:
I do think I will start off preparing the LFS tools and then begin Slackware on top of that. (using Slackware sources where I can to start.)

Goals:
1. Make it as much like Slackware as possible - especially in PKG management
2. Be able to upgrade along with the Slackware upgrade path since I'll be using it on other PCs too (even if I have to recompile)
3. Make a Cross-Compiler for x86, x64, PPC, Embedded ARM with DISTCC on all my platforms
4. Do some custom c/c++ development that is cross-platform (Arch and OS)
5. MOST IMPORTANT: Tinker because I can... =D

You should see this article by Alien Bob after 64-bit Slackware was made public (unfortunately you now are required to sign up to read the article, and they ask some very intrusive questions...). In particular he mentions using CLFS to create the initial environment. Since there technically is a base to start from (Gentoo I guess) you could probably get away without needing to start with cross compilation and instead upgrade core packages bit by bit and expand the system out, but it won't be very clean and you'll have to try to sterilize the system of old junk afterward (assuming you want a 100% clean Slackware port). Either way you'll have to make a few passes over some packages...LFS/CLFS is definitely a good start, and once the environment is capable enough you can start using SlackBuilds to create packages (and then rebuilding the initial environment to support Slackware packages).

It's a lot easier to maintain an existing system than to build one from scratch, so the initial work is definitely going to be the trickiest and I wish you luck if you are determined to continue. Although I have no use for PPC-Slackware, I'm sure the community could benefit if you share your work.

slackintosh-current seems pretty much up-to-date...

(I won't be signing up to read the article although I probably should...)

Thanks. I'll be installing all new packages on a new drive so I should be able to keep it 'fairly' clean... =D

You are right - I could update the gentoo dist enough to be able to run the SlackBuilds and then install them to the second drive, boot into the drive (reboot or chroot) and then rebuild it all again and, in theory, make a clean Slackware install =D... In theory...

I have two issues here:
1. I can't get the thing to boot...
2. It's last update was well over a year ago...

I will use it as a reference if some packages won't compile or I find I need other packages.

The last update to Slackintosh -current was October 2010. I suppose that is technically a year ago now...but perhaps we could give them a bit more credit.

Sorry about that... I was going off of the news page and I mis-read the changelog date.
I still can't boot the CD image and I do plan to use it as a reference if I can't get everything to compile.