-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
netcdf-c #132
Comments
@ngam note that I'd love to rename but this is one of those places where a bad choice needs to be maintained b/c changing out be way more disruptive. Note that we, conda-forge, did not choose that. We inherited it from defaults and kept the same name to be compatible with the main channel. |
Yes, I understand and I am NOT in favor of renaming (because it would be highly disruptive). I was thinking we could have an alias. I tried looking into it and I realized a possibility would be to just output this twice (like I did here: conda-forge/coreutils-feedstock#23) but that would also be unnecessarily redundant? Hence, closing... happy to submit a PR to split it into two outputs if you think it is worth it :) |
Or maybe we could have a meta package ... that would be pretty easy, but again, it might set a bad precedent with people submitting meta packages like that all over the place |
I created a few aliases packages with a meta package that installs the canonical one. So, netcdf-c, would install libnetcdf-c. That is IMO, the easiest solution b/c you avoid duplicated builds. However, after making a few of those for Python packages with TL;DR I'm not against it and I can help review a PR but I'm not sure the effort is worth it. |
Other places (e.g. spack.io) call this netcdf-c rather than libnetcdf. Can we add an alias or something, to be fully consistent with netcdf-fortran and other providers? Thanks!
Issue:
Environment (
conda list
):Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: