Added eko as git submodule.

[alecandido]

The actual branch in which adding the eko dependency.

[scarlehoff]

Why is a specific commit needed?

[alecandido]

@scarlehoff I need a specific commit because some functions currently used in dis are already deprecated in dis.

In order to do things by sequential steps I'm trying to checkout the last commit in which they were still present in eko, rather than fixing dis logic in order to fix continuous integration.

[alecandido]

Still to be solved:

• problem with version in meta.yaml (not able to compile jinja template even if git describe --tags available)
• the problem: conda build fails with a stack trace barely readable dd3a988

[alecandido]

One (fake) solution:

• rule out conda-recipe and use conda manually to install apfel and lhapdf only
• is working as long as we don't have to deploy
• if we have to deploy somewhere we are writing a full python package, and if there will be no final dependence on lhapdf we can deploy directly on PyPI, fully avoiding conda

This is not the solution that I want to achieve right now, but I liked to write it here because is still solution, and I'm quite annoyed by fixing stuffs inside conda.

[alecandido]

@scarrazza when you will be again available I would like to listen also to your opinion, please :)

[alecandido]

Ok, I think I'm ready:

• I removed any conda-build trace
• now the workflow is perfectly working with eko
  If the reviewers agree we can merge this into the other branch ('docker-to-conda-action') and than in the master (or the other way: the other into the master and this into the master too).

Thank you @scarlehoff to help me trying to fix it with conda-build, and thank you very much @scarrazza to make me free of that.