Hi Fotis,
Thanks for the suggestion. Is it also possible to use this feature for
dependencies, i.e. when a config needs a new version of a program for which
only eb files for older versions are available?
Best regards,
Toon
On 08/05/2013 01:05 PM, Fotis Georgatos wrote:
Hi Toon,
On Aug 5, 2013, at 12:21 PM, Toon Verstraelen wrote:
Cython is also a package that evolves very rapidly with a (significant) new
release every one or two months. So, I'll include these configs in a pull
request, right?
One piece of info that maybe relevant here (or, perhaps for future needs):
* A very nice and generic feature of EB are the --try-* options
If the build procedure of the new Cython is not deviating much from an existing
easyconfig,
you can on the fly "calculate" the new easyconfig with
--try-software-version=XYZ;
the same idea applies for --try-toolchain=* and a few more bits and just works
fine!
So, if the easyconfig you want does not exist already (check with eb --search),
simply pick the closest example and use the --try-* parameters, as you deem
fit...
cheers,
Fotis
