post-build version numbers about conda-build HOT 20 CLOSED

Ah, so the version is there before the build, but it's not easy to get at because you can't just import dynd; dynd.__version__?

from conda-build.

No, the version isn't there before the build, it gets constructed from a 'git describe' call during the build, and can be retrieved from the package at that point.

from conda-build.

I see. We should probably allow a similar thing for the build string.

How should we implement it? Maybe some flag that indicates to get the version from some environment variable, which is set in the build script.

from conda-build.

Having the build script set it in an environment variable would work well, sure.

from conda-build.

Thoughts how to do this @ilanschnell?

from conda-build.

If the build script sets an environment variable, how can we access it after the build script is finished?

from conda-build.

If that's not feasible, I guess a different approach is needed

from conda-build.

The build script write a special file, e.g. named __version_build__.txt, into the source directory. If conda-build sees this file after the build script is executed, it adjusts the version and build number accordingly.

from conda-build.

Why not call it __version__.txt? --- Alternatively the build script or meta.yaml file could specify the name of the file to look for.

Do you always have write access to the source directory? Perhaps we can look for this in the build directory instead?

from conda-build.

The source directory is where things get build usually. There is always write access to the source directory, for example when you extract a tarball, you need to be able to write files like config.log, build/, or even apply patches to the source.

from conda-build.

Actually, one needs the ability to extract the source tarball there in the first place.

from conda-build.

Good point, Aaron!

from conda-build.

What should be placed in the meta.yaml for the version in this case? Nothing? A special placeholder?

from conda-build.

I would argue that nothing extra is put into the meta.yaml file. There can even be a version in it, but as soon as the special file is found, it uses that.

from conda-build.

OK, that is simple enough.

from conda-build.

I disagree, I think a special tag should go in the meta.yaml, so that if a bug prevents the version file creation, an error is raised instead of silently producing a junk version.

from conda-build.

I just tested this new feature and can verify that it works as expected.

from conda-build.

I have also updated the docs.

from conda-build.

Just as a reference, __conda_version__.txt is the name we decided on.

from conda-build.

Hi there, thank you for your contribution!

This issue has been automatically locked because it has not had recent activity after being closed.

Please open a new issue if needed.

Thanks!

from conda-build.