2010/12/3 Michael K. Johnson <johns...@rpath.com>: > On Fri, Dec 03, 2010 at 06:49:13PM +0100, Bertrand Juglas wrote: >> Le 3 déc. 2010 à 16:15, "Michael K. Johnson" <johns...@rpath.com> a écrit : >> > You say you documented it -- I don't recall seeing the summary sent to >> > this list. >> It's on http://www.netinfolution.info/pack/sujet/conary > > Ah, sorry I missed that before. > >> When conary runs well on F14, do i need rmake too on F14 ? Or rmake should >> better be used on native conary platforms? > > No need for rmake to do this import. It's something we could consider > after the import, if we want to (say) allow you to use Fedora systems > to run rmake nodes, but that would definitely be something to worry > about later if anyone cares. > >> I've cloned the mirrorball and your Fedora config for it but i don't know >> what to do next, that's why i've stopped :( > > The next thing is to start a repository and build libelf-lgpl and > conary packages into it by hand, for both 32-bit and 64-bit. > > So you create a repository (using rBuilder Online is fine for this) > and create a new package called libelf-lgpl in it. Use the rPL > recipe for libelf-lgpl as a starting point. Don't worry about > buildRequires for now -- those will get fixed later. Build the > recipe with --no-deps until it builds. Check in the source. > > Then separately on 32-bit and 64-bit systems, you run the command: > $ cvc cook libelf-lgpl --install-label=LABELINYOURREPO --no-deps > Obviously, if it breaks, you fix the source and build again. > (Note that the 32-bit machine can be a 32-bit chroot on a 64-bit > machine; you'll need to use "setarch chroot" to get into the chroot > so that you're showing the right architecture in the chroot.) > > Once you have that built, on each machine, you'll need to install > the libelf-lgpl you built, using conary. This means using the > conary chroot you built as root: > # cd /path/to/your/conary/checkout > # conary update --no-deps libelf-lgpl=LABELINYOURREPO > > Now you're set to do exactly the same thing with conary that you > just went through with libelf. Again, don't worry about buildRequires. > Use Foresight 2 as the source of your recipe for conary. When that's > done, do the same thing with conary-policy.
Now that you've precised it here by email, I will clean and update my wiki page to report what i've run to make the import of F14 on F14 itself. Do you think i should migrate this wiki page on Foresight wiki to let all Foresight community contribute to it and begin using the same syntax as other wiki pages ? _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
