Dear Jakob, Thanks for the suggestion. I had originally thought that it would be cleaner to keep the configuration information directly in the EasyConfig, but obviously a patch would use a well-established method.
Nevertheless I must admit that patching a non-existent file into being seems to me to be stretching the concept of a 'patch' somewhat bit :-) Cheers, Loris Jakob Schiøtz <[email protected]> writes: > Dear Loris, > > I have been doing it by making a patch (between /dev/null and the actual > file), > and add that patch to the easybuild config. See e.g. the files for > GPAW-19-8-1 > in the develop branch (or the merged pull request here: > https://github.com/easybuilders/easybuild-easyconfigs/pull/8768/files ) > > Best regards > > Jakob > > >> On 26 Aug 2019, at 9:32, Loris Bennett <[email protected]> wrote: >> >> Hi, >> >> If I need to create a new file as part of the installation, such as a >> config file, what is the canonical way of doing this? Do I just echo >> the information to a file in 'install_cmd' or, probably better, >> 'postinstallcmds'[1]? Or is there some more pythonic approach? >> >> Cheers, >> >> Loris >> >> Footnotes: >> [1] Would it make sense to consolidate the naming scheme, e.g. to replace >> 'postinstallcmds' with 'postinstall_cmd'? >> >> -- >> Dr. Loris Bennett (Mr.) >> ZEDAT, Freie Universität Berlin Email [email protected] > > -- > Jakob Schiøtz, professor, Ph.D. > Department of Physics > Technical University of Denmark > DK-2800 Kongens Lyngby, Denmark > http://www.fysik.dtu.dk/~schiotz/ > > > -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email [email protected]
