Hi Kenneth, Thanks for letting me know, I’ve updated my easyconfig file…
— Regards, Franky Op 30-apr.-2015, om 20:45 heeft Kenneth Hoste <[email protected]<mailto:[email protected]>> het volgende geschreven: On 30/04/15 10:09, Backeljauw Franky wrote: Hi Jens, Op 30-apr.-2015, om 09:53 heeft Jens Timmerman <[email protected]<mailto:[email protected]>> het volgende geschreven: On 29/04/15 17:15, Backeljauw Franky wrote: I have a small question: after unpacking a tar-file of a PythonPackage, I need to add a file to its directory before starting the build process. How can I do that with EasyBuild? I tried with a patch as in “diff -ru -NB” but that tells me it cannot determine the patch level… Any ideas? I've seen Kenneth do it like this patches = [ 'somepatch,patch', ['filetocopy', 'directory to copy it to, e.g, ./somedir'] ] This last construction worked: patches = [‘build.conf’,’./‘] This works, but it doesn't do what you think it does. :-) What Jens was suggesting is this: patches = [('build.conf', '.')] That is: tell EasyBuild to *copy* the file build.conf to whatever the current directory is at that time. EasyBuild knows it should copy this file rather than try to treat it as a patch file, because the filename doesn't end with .patch . Since the default target is '.', this should be the same as: patches = ['build.conf'] What you are doing is copying both 'build.conf' and '.' to the current directory. Apparently the Python equivalent of "cp . ." 'works' fine, but you just got lucky there. ;-) TL;DR: We need to get the various options for 'patches' documented, there are other things too you can do (e.g., supply the patch level to use for patch files, or the location where patch files should be applied in). K.
