Hi.
As I said, I am polishing my build scripts (specially the post-installation stuff). I make my own Slackware-based distro for my personal use, so I like to compile some things, make .tgz packages, make them into series and add them to my installer CDs. (take a look at "Cooking up some Slackware - CUSS). So far, I am figuring out how to make more efficient the part that automatically generates the default gconf entries under /etc/gconf/gconf.xml.defaults.
As soon as I think they are (the SlackBuilds) "stable" enough, I will make them public.
Quote:
Do your scripts automatically download all the required packages & dependancies?
|
No, I do NOT download the packages and dependencies automatically, BUT I do keep a list of those dependencies and the places where they can be found. Don't fear, there aren't too much.
I am planning to make two versions: one with every package built stand-alone and the second (the way I like it) with "cousin" packages merged into big packages (this is, the series they are built of from: gnome-platform, gnome-bindings, etc). I don't like having hundreds of packages wandering inside /var/log/packages.
I focused on building a MINIMAL install as close as possible to the original sources. (the way GNOME was built when it was officially built in Slackware). I think perhaps that's why it didn't cost me so much - I mean, finding extra dependencies for extra software.
I still have to figure how to correctly compile epiphany and yelp.
Thanks a lot for your interest. It is encouraging.