cannot specify any version and build about condapkg.jl HOT 4 CLOSED

CondaPkg does not promise (so far) to follow the same package specs as the Conda command line, so it's not a bug that tensorflow=*=cpu* is not supported. In fact the CondaPkg REPL syntax is very under-specified right now - sort of intentionally.

For your specific case, you can already do conda add 'tensorflow >0 cpu*' or CondaPkg.add("tensorflow", build="cpu*").

On the one hand, it is nice to support familiar syntax for Conda users. On the other hand, the pkg=version=build syntax has the drawback that it limits what versions are allowed (e.g. you can't specify the version as >=3,<4 because those extra =s confuse things) and the pkg=version syntax is special in that foo=3.8 actually parses the version as 3.8.*.

Also, CondaPkg generally tries to stick to conventions from Pkg. So I propose specifying the build with a #, e.g. conda add tensorflow#cpu*.

What do you think?

from condapkg.jl.

For your specific case, you can already do conda add 'tensorflow >0 cpu*' or CondaPkg.add("tensorflow", build="cpu*").

Thanks, I didn't know that, and it might be worth to add some test or some documentation examples for the users.

the pkg=version=build syntax has the drawback that it limits what versions are allowed (e.g. you can't specify the version as >=3,<4 because those extra =s confuse things)

Yes, imo using a = is a poor choice from the conda developers in the first place.

I would tend to agree with the choice of using add instead or install for consistency with Pkg. In fact, we could use @1.2 for version specifiers and as you proposed #cpu* for a build spec, and try to stick with the Pkg conventions. Of course, this would need docs.

from condapkg.jl.

FYI #59 implements this suggestion.

from condapkg.jl.

Great, thanks for the prompt fix and the new release ;)

from condapkg.jl.