Started by NCommander, March 14, 2017, 10:51:02 AM
Quote from: evolver56k on July 02, 2019, 12:42:42 PMYou can create a 'manifest file' from the extracted tarballs from something like this where you extracted them (if using a bourne shell): Code Select Expandfor i in $(ls -1) ; do echo "dir $i all" >> buildmanifest.txtand using: Code Select Expanddarwin-buildall buildmanifest.txt /path/to/debrepo /path/to/debdestinationWill build all the packages it can, and automatically deleting the temp files under /tmp/roots/ on a successful build. The third field of the manifest is the same as the --target flag for darwin-buildpackage, so it can be any of all|headers|objs|localThere's a Manifest file on the Darwin 0.3 disc (Darwin OS Install CD/Binary Packages/Manifest ... it has mac line endings, so you'll have to change those to unix line endings first before using it with buildall, and change ^cvs to dir) that I believe shows how they built the deb packages for the release
for i in $(ls -1) ; do echo "dir $i all" >> buildmanifest.txt
darwin-buildall buildmanifest.txt /path/to/debrepo /path/to/debdestination
Quote from: evolver56k on February 04, 2021, 10:18:43 AMI have had a github repo set up for this for a while now, but recently made it public. I've gotten the entire Darwin 0.3 sources to build fat binaries on both intel and ppc installs, and have a binary tarball from an early build run as a release, which can be used for the binary repo during building.