Hi, I'm using EasyBuild 2.3.0 and are wanting to build Cufflinks. We tried the Cufflinks-2.2.1-goolf-1.4.10.eb on CentOS and the build fails. Fixing the the build falls into one of several categories: * patch GCC 4.7.2 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52903) * update goolf-1.4.10 to use GCC 4.7.3 (fixes the bug in 4.7.2) * create a new Cufflinks easyconfig based on goolf-1.7.20
As a learning exercise, I'm following each path. (BTW, I do plan to submit pull requests once my builds are verified.) In doing so, I'm wondering if there are there any recommended practices for updating and easyconfig that has a bug, changing a compiler version dependency or introducing new easyconfigs. I assume the git-hooks are designed to allow sites to build against pending upstream commits using the "build against pull request feature". I haven't seen much in the way of recommendations for handling the local environment to make contributing easier. For example, how to install the easyconfig or blocks so that I can work against a git clone'd tree (I'm currently using a symlink to the repo easyconfig dir inside my personal easybuid env). Given that the easyconfigs are all distributed from upstream in one big chunk vs. individual repos, I may have a need to maintain local variations that don't make it into the upstream or aren't appropriate for it. What approaches do you recommend for handling these situations? Thanks, ~jpr
