Template files with -FULL suffix, rename target file also (exs: in coreutils, util-linux).Īny dir in template with PKGVERSION in name, substitute actual pkg version number in target dir.Non-zero file, means copy this file from template to target.0-size file, means get file of same name from deb (even if in different dir) to target.Exception, file named PLUSEXTRAFILES then target will have all files from deb. packages-templates directoryĪny directory in the template, the files in the target pkg will be cut down to the same selection (even if empty dir). Woof-CE (woof-Community Edition) is a fork of Barry Kauler's woof2 fossil repository of commit f6332edbc4a75c262a8fec6e7d39229b0acf32cd.
Puppy linux iso file iso#
This gets built in a directory named sandbox3 and as well as the live-CD ISO file you will also find the individual built files and the devx file. So, to get going with woof-CE, open a terminal and do this: So, you create woof-out without any confusing inappropriate content. You can choose the host system that you are building on (usually x86_64), the target (exs: x86_64 x86, ARM), the compatible-distro (ex: slackware), and the compat-distro version (ex: 15.0). The great thing about this merge operation is that you can choose exactly what you want to go into woof-out. You then cd into woof-out_* and run the build scripts. This merges the 5 directories into a directory named woof-out_*. To create a working directory, named woof-out_*, you first have to run the merge2out script. initrd-progs: scripts and files to generate the initial ramdisk.kernel-kit : scripts to download, patch, configure and build the kernel.woof-distro : distro-configuration (Debian, Slackware, etc.) files.woof-arch : architecture-dependent (x86_64, x86, ARM) files, mostly binary executables.To work on woof-CE in a fork, through Gitpod: Not all of woof-CE can run without root access, but most of woof-CE works on Gitpod and it's possible to boot Puppy inside QEMU and control it over VNC, all through the browser. To modify woof-CE and push the changes to GitHub without having to set up a local development environment: Test your Puppy and open a pull request to woof-CE, if you want your changes to be officially incorporated into woof-CE. Modify woof-CE, commit your changes and push them.ĭownload your Puppy from the newly published release.
Puppy can be built directly on GitHub, saving the hassle of preparing a suitable build environment on a fast machine with adequate storage.
0 kommentar(er)
