On Mon, Jan 27, 2014 at 10:26:35PM -0500, Michael K. Johnson wrote: > With those bootstrap imports finished, we'll be able to use > mirrorball normally do build packages and groups. The group > structure will look a lot like you might have seen in the CentOS > import before, though instead of group-rpath-packages for the > Conary-related tools, we'll probably go with group-conary-packages
since not all of us have seen the centos import, could you elaborate on this just a bit? > Many of the problems we'll run into will be discovered after one > round of package importing when we are trying to build groups and > discover that the encapsulated packages are not conary-dep-complete. so most of the expected problems will be missing dependencies? how will these be detected? many dependencies as far as i can tell only show up at runtime. > After we can build groups, we'll be able to do things like import > updates; right now, we're sticking with the initial release of F20 > with no updates. We really want all the initial packages in the > repository to make it easy to "adopt" systems that were installed > from the original media. Mirrorball will drive that update process. will we try to import every version of updates or just the latest ones available when the update runs? greetings, martin. -- eKita - the online platform for your entire academic life hackerspace beijing - http://qike.info -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net foresight developer realss.com foresightlinux.org unix sysadmin trainer developer societyserver.org Martin Bähr working in china http://societyserver.org/mbaehr/ _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
