-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add to conda-forge repository #9
Comments
It's open source software so you can do what you like with it (provided of course that you read and follow the license conditions). You don't need our approval. Saxon-HE is built into hundreds of other packages, most of which (like Conda) we have never heard of. We would encourage you to do it in a way that keeps up with new versions and maintenance releases as they appear. |
We're working on our Python infrastructure tooling at the moment, and Conda is on our radar, but we haven't figured out how PE and EE might fit into that too, as well as precisely which Saxon version (java or python) would be appropriate for Conda. I'll take a look at your PR/recipe with interest and we'll try and address conda-forge more directly when we're a bit further along with our work. Thanks for taking an interest! |
@michaelhkay Thank you for your kind response! I will merge it as soon as the conda-forge maintainer approves my PR. @fidothe Thank you for your informative comments! My motivation is to use |
Hello!
In order to facilitate installing
saxon-he
for conda-ecosystem users, I would like to suggest to upload it to the conda-forge repository.I am sorry for letting you know nothing, but I already made the PR, ready to deploy.
Currently, I am only listed as a maintainer for its "recipe," so I would appreciate it if you would propose any potential members.
Many thanks for considering my request.
The official issue tracker for Saxonica products is saxonica.plan.io. Please only use the issue tracker here at GitHub to report issues with the Saxon-HE distribution archives in this repository.
The text was updated successfully, but these errors were encountered: