Re: [easybuild] Fixing versions for standard dependencies beyond the toolchains

2017-12-20 Thread Kenneth Hoste
On 20/12/2017 08:31, Åke Sandgren wrote: On 12/20/2017 08:17 AM, Kenneth Hoste wrote: On 11/12/2017 16:30, Erik Smeets wrote: Hi, The strict versioning scheme now is both a blessing and a curse: it's a way of communicating that a particular combinations of versions worked, but it does result

Re: [easybuild] Fixing versions for standard dependencies beyond the toolchains

2017-12-19 Thread Kenneth Hoste
On 11/12/2017 16:30, Erik Smeets wrote: Hi, There are also a lot of dependencies to applications that in my opinion don't need a specific toolchain, but just need to be available. Maybe don't add these to a specific toolchain or version, but a generally avaible toolchain (dummy?). There's

Re: [easybuild] Fixing versions for standard dependencies beyond the toolchains

2017-12-12 Thread Alan O'Cais
Hi Erik, Yes, this has been discussed a few times before and definitely many people would like to see this feature but the implementation is the tricky part. Having said that, the implementation may be getting more feasible. For toolchain resolution we already have a search in place based on

Re: [easybuild] Fixing versions for standard dependencies beyond the toolchains

2017-12-11 Thread Erik Smeets
Hi, There are also a lot of dependencies to applications that in my opinion don't need a specific toolchain, but just need to be available. Maybe don't add these to a specific toolchain or version, but a generally avaible toolchain (dummy?). Also, now dependencies are really strict on version,

Re: [easybuild] Fixing versions for standard dependencies beyond the toolchains

2017-11-24 Thread Åke Sandgren
It's fairly simple. Use whatever is already available for the selected toolchain. Don't forget to check the git develop branch and any pending PRs when deciding on versions. On 11/24/2017 10:16 AM, Joachim Hein wrote: > Hi, > > Because of interoperability of software, I see an increasing need