Hi Marius, Mark, > Only packages with a large impact in terms of rebuilds (as calculated by > `guix refresh -l <package-name>`). Obviously gcc is one such package.
> http://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html Thanks! That is exactly the information I was looking for. > Most changes go to 'master' first and are later merged into > 'core-updates'. However, changes that would force a large number of > rebuilds need to be pushed to another branch, to allow our build farm to > rebuild before its merged to 'master'. Understood, makes a lot of sense. > If you are porting to a new architecture, I would definitely recommend > basing your work on 'core-updates', which will likely be merged into > 'master' in the next two weeks. If you need gcc-4.9.4, that's another > reason to base your work on 'core-updates'. I am (I think) almost there, I expect to be able to succesfully build hello on my ppc machine soon (it's a slow machine, so iterations take time). I do not feel like changing to core-updates now (though I would have been better had I worked there since the beggining). Once I have bootstrapped, I will review the changes and rebase the "core" ones to core-updates. I should be there before two weeks' time. Thanks! Carlos
