Puppy Linux Discussion Forum

[playdayz]

I have put in quite a few hours and tested, but let's call it a beta for now.

Using Woof to build Lucid Puppy 5.2

All that’s needed is a fast internet connection, 5GB or more of disk space, and some time

It is not an *identical* copy of Lucid 5.2, because it is using the current Woof rather than the Woof that was actually used to build Lucid 5.2, but that is one of the advantages of the Woof build system, to be able to incorporate the updates Barry has made in the latest Woof.

Additionally Lucid 5.2 is more of a hybrid than previous versions of Lucid--it has many packages from Maverick as well as packages that were compiled in Lucid as well as some that were even compiled in other versions. This is the main reason for the longer development time, to catch any bugs that the diversity introduced. IMHO we were very successful at that and I believe Lucid 5.2 has the fewest bugs of all Lucid versions--it is also the most complicated and there might be something I missed in preparing this Woof build. I noticed that pmusic and probably other packages actually went backward from Lucid 5.2--but that is what the current Woof calls for--it happens because many packages were updated by hand for Lucid 5.2 and it will change when the next Woof is posted.

1. Install Woof. http://bkhome.org/bones/
2. Download the DISTRO_PKGS_SPECS_ubuntu_lucid file, unpack, and copy it into your woof-tree directory. http://diddywahdiddy.net/Puppy500/DISTRO_PKGS_SPECS-ubuntu-lucid.tar.gz It is important to use this one if the goal is to produce Lucid 5.2 rather than a more generic Upup. Packages such as 'abiword_lucid52' are custom packages for Lucid 5.2.
3. Start woof-gui.
a. Set the Specs
b. Download the dbs. This takes a while to convert the Ubuntu databases.
c. Download the pkgs. This doesn’t take as long as one would think.
d. Build the packages. This takes longer than one would think--over an hour.
e. Kernel options: kernel linux_kernel-2.6.33.2-tickless_smp_patched-L3.pet. (Lucid 5.2 uses ‘tick to erase framebuffer modules’ and ‘tick to erase exotic modules’, but the exotic modules should probably be included--though we have had only one problem reported because they were not included.)
f. Build Distro. Doesn’t take long at all. You will make some choices about theme, etc.
g. Can burn to disk or use files from /woof-tree/sandbox3/build in frugal install.
h. Use the standard devx because I haven’t worked on that in this Woof yet.

The "Cheats" I use

The packages such as abiword_lucid52 are packages that have been manually tweaked. They might be packages from maverick or natty, or packages compiled in Puppy. gnumeric_lucid52, for instance, was compiled by ttuuxxx. They may also contain manual adjustments to lucid packages. Using these packages is the way to get a very close copy of Lucid 52.

[playdayz]

Oh Man, and I was happy someone had finally replied to this one.

Ah, our fine moderator killed the spam. Thanks!

[sc0ttman]

Actually I just found this, from a link you posted in another thread, about remastering methods.

I like the list of steps to be taken - looks simple!

(I still don't have the required space, but will save this info for later!)

[scsijon]

give me time playdayz, I only found it saturday (and just as I was running out of sat useage too) .

downloading......

questions to follow

thanks for doing it.

scsijon

[scsijon]

download-errors file

[playdayz]

[scsijon]

good, that works now, thanks, was under the impression that part of the diff files included the database updates.

decided I won't update woof again for my puppy version until I have a releasable stage1 alpha (standard frame) unless someone finds a major build problem that will effect my forward path.

thanks again
scsijon