Hi! csanchez...@gmail.com (Carlos Sánchez de La Lama) skribis:
>> I ended up splitting it in 3 patches (gcc, linux-libre, and >> glibc-dynamic-linker) that I just pushed to ‘core-updates’. I also >> added copyright lines for you where appropriate. Hope that’s fine! > > Thats perfect :) > >>> I think the best way to proceed is integrate this onto core-updates >>> (once reviewed & approved), then generate a bootstrap binaries on hydra, >>> making them available for download on the bootstrap binaries URL. At >>> that point I can update the rest of the powerpc-linux-gnu patches (which >>> use this binaries) with the correct hashes, and send them to the list. >> >> Sounds like a good plan. >> >> Commit 9410a5aa916035bb4d7f032a5fe81cfb497887c8 adds powerpc-linux-gnu >> cross-builds for Hydra (though Hydra is currently busy with the >> ‘staging’ branch.) > > Nice! I will generate the bootstrap tarballs locally using that commit > to check everything target-side works, before hydra time is spent on > that. If everything goes all right, I will then update the powerpc > patches with the new hashes (and the expected URL for the binaries), so > any powerpc user can jump in and use/test GUIX. Sounds good! >>> As Ludo suggested, I am also preparing a tutorial/blog on the porting >>> process. >> >> Awesome! > > It is getting a little bit more complex than expected, and my time > allowance also shorter. I am writting a set of "steps" on how I made the > porting, including all the debugging I had to do, so what is already > written might be useful as it is (not only as a porting guide but also > as an example of GUIX hacking). Do you think it makes sense to publish > it already so I can complete it later? Or better wait till it is > finished? Up to you! If you have something that’s self-contained and intelligible to people who don’t have your experience, that’s probably fine. Cheers, Ludo’.
