On Fri, Dec 20, 2013 at 06:52:49AM -0500, Michael K. Johnson wrote: > I'll give you an idea from my older experience. What Brett > tells you (soon, I hope...) will generally trump what I say, > as he's been the main one actively doing this for the past few > years. But I'll do what I can.
That was about right. Here's a more detailed view of the tasks, following up from a lunch discussion with Brett. The following two steps don't require any mirrorball knowledge and are prerequisites to doing meaningful work on this project. Don't have to wait for Conary repositories and mirrorball docs. Create a 64-bit Fedora 20 chroot environment of a complete development system, including all the Conary prerequisites. Do an install into a VM, and test using "make" in a Conary checkout, adding missing dependencies until Conary builds, then copy the filesystem out into an archive from which we can build a chroot to do the bootstrapping. (Volunteers?) Mirror the RPM and SRPM yum repositories. There is an rsync script in mirrorball that's a good starting point. See scripts/sync-fedora.sh for details. (I'll start a sync process to fdev:/srv/mirror/ and let it run under cron. That will take a while...) Set up two Conary repositories: * One ephemeral repository that can be thrown away after the bootstrap process is finished * One to be a permanent f20 repository. We'll use a separate repository for each import, to make mirroring and space management in general easier. More on the bootstrap process: * Build conary, rmake, etc. in the F20 chroot environment, and (as previously discussed) commit them into a first bootstrap label in the ephemeral repository using "cvc cook". * Use "cvc cook" to build the encapsulated packages included in a minimal install of F20, plus build requirements for conary and rmake, onto that first bootstrap label. * Use mirrorball driving rmake to build those same packages onto a second bootstrap label, demonstrating that we got all the packages we needed for the first stage bootstrap. * Use mirrorball driving rmake to build the whole F20 distro, both 64-bit and 32-bit (but not arm unless someone donates a bunch of arm servers...) onto the production label. We'll probably want to have mirrorball parse the yum groups and generate conary groups based on the yum groups. There might be code to do this? We will use only a single label, not devel/qa/production promotion. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
