Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conda forge version and entwine version #324

Open
trns1997 opened this issue Aug 1, 2024 · 2 comments
Open

Conda forge version and entwine version #324

trns1997 opened this issue Aug 1, 2024 · 2 comments

Comments

@trns1997
Copy link

trns1997 commented Aug 1, 2024

Just curious, is there a reason why the version of entwine when installed via conda-forge like:

conda create --yes --name entwine --channel conda-forge entwine=3.0.0

does not correspond to the version in the env:

(entwine) builder@090a3d808cfa:~/workspace$ entwine --version
Invalid app type
    Version: 2.3.0
    Usage: entwine <app> <options>
    Apps:
        build
            Build an EPT dataset
        merge
            Merge colocated entwine subsets
        info
            Gather metadata information about point cloud files

And for version 3.1.1:

conda create --yes --name entwine --channel conda-forge entwine=3.1.1
(entwine) builder@a16474e7ede1:~/workspace$ entwine --version
Invalid app type
    Version: 3.1.0
    Usage: entwine <app> <options>
    Apps:
        build
            Build an EPT dataset
        merge
            Merge colocated entwine subsets
        info
            Gather metadata information about point cloud files

@hobu
Copy link
Collaborator

hobu commented Aug 2, 2024

Just curious, is there a reason why the version of entwine when installed via conda-forge does not correspond to the version in the env:

Because the person who makes the releases forgets to update the version number before doing so and you've found the two times it has happened 😂

@trns1997
Copy link
Author

trns1997 commented Aug 2, 2024

Well it is good to know. I guess something to keep in mind for the next release hahaha. Maybe add a step in the pipeline for releases that modifies the version based on the tag? Let me know if it interests you guys, if i have time i can look into it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants