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/DISTR ... cid.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.
How to Use Woof to Build Lucid Puppy 5.2
How to Use Woof to Build Lucid Puppy 5.2
Last edited by playdayz on Tue 01 Mar 2011, 22:09, edited 1 time in total.
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!)
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!)
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
problem or a missing source?
download-errors file
any idea where I can fix this? and get them.
thanks
scsijon
Code: Select all
GENERICNAME=abiword_lucid52 however PET package not found.
GENERICNAME=browser-default_lucid52 however PET package not found.
GENERICNAME=cups_lucid52 however PET package not found.
GENERICNAME=dillo_lucid52 however PET package not found.
GENERICNAME=ffmpeg_lucid52 however PET package not found.
GENERICNAME=firewallstate_lucid52 however PET package not found.
GENERICNAME=firstrun_lucid52 however PET package not found.
GENERICNAME=freememapplet_tray_lucid52 however PET package not found.
GENERICNAME=gcalctool_lucid52 however PET package not found.
GENERICNAME=geany_lucid52 however PET package not found.
GENERICNAME=ghostscript_lucid52 however PET package not found.
GENERICNAME=gnome-mplayer_lucid52 however PET package not found.
GENERICNAME=gnumeric_lucid52 however PET package not found.
GENERICNAME=goffice_lucid52 however PET package not found.
GENERICNAME=midori-cups_lucid52 however PET package not found.
GENERICNAME=mplayer_lucid52 however PET package not found.
GENERICNAME=mtpaint_lucid52 however PET package not found.
GENERICNAME=network_tray_lucid52 however PET package not found.
GENERICNAME=new_themes_lucid52 however PET package not found.
GENERICNAME=p7zipxz_lucid52 however PET package not found.
GENERICNAME=PupClockset_lucid52 however PET package not found.
GENERICNAME=quickpet_lucid52 however PET package not found.
GENERICNAME=retrovol_lucid52 however PET package not found.
GENERICNAME=Send-to-backgrounds_lucid52 however PET package not found.
GENERICNAME=sylpheed_lucid52 however PET package not found.
GENERICNAME=unrar_lucid52 however PET package not found.
GENERICNAME=wcpufreq_lucid52 however PET package not found.
GENERICNAME=wmswitcher_lucid52 however PET package not found.
GENERICNAME=xorg_base_lucid52 however PET package not found.
GENERICNAME=xserver_xorg_lucid52 however PET package not found.
GENERICNAME=zsynclient-wrapper_lucid52 however PET package not found.
GENERICNAME=zzLupu_Utilities_lucid52 however PET package not found.
thanks
scsijon
scsijon, Use this Packages-puppy5-official. Delete the phony .gz and put it into your Woof directory replacing the one that is there--and also put it into your /root/.packages directory (I am not sure which one is used). You could also choose to Update db's in Woof and that would grab it too.download-errors file
Good luck, Keep asking questions, pm me, Larry
- Attachments
-
- Packages-puppy-5-official.gz
- (24.15 KiB) Downloaded 536 times
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
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