https://github.com/arup-group/conda-recipes
Recipes to create conda packages for use by the City Modelling Lab
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (11.7%) to scientific vocabulary
Repository
Recipes to create conda packages for use by the City Modelling Lab
Basic Info
- Host: GitHub
- Owner: arup-group
- License: mit
- Default Branch: main
- Size: 62.5 KB
Statistics
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 2
- Releases: 0
Metadata Files
README.md
conda-recipes
Recipes to create conda packages for use by the City Modelling Lab.
NOTE: these packages reside here because the process of getting packages added to the conda-forge channel can be very slow.
You should also contribute the package to conda-forge according to their instructions here.
Once it has been incorporated into conda-forge, you can delete it from here.
These packages already exist on PyPi (i.e., they are pip installable), but we require them as conda dependencies.
Adding a new recipe
Each directory should contain a LICENSE file and a meta.yaml configuration file.
For an example of a Python-only configuration, see s2sphere.
For an example Python binding to a C library, see osmium.
Note that this particular binding example has all the hard work done in the upstream repository, so we don't have to handle any of the bash scripting ourselves.
Each new recipe should be added from a new branch via a PR. During the pull request process, the packages will be built and will throw errors if there is something wrong with your recipe. Only merge in PRs once all CI passes. Once merged, the packages will be uploaded to Anaconda.
NOTE: if you are building a package for each operating system separately, you cannot build for OSX-ARM64 as there are no appropriate GitHub runners for this.
You will need to run conda build locally from an Apple Silicon device (any from after 2020) and upload the resulting built package yourself.
Updating an existing recipe
For a new version:
1. update the version number and pip tarball SHA key
2. update any dependencies and their version pins
3. return the build number to 0 if set to a higher number.
If you realise there is a problem with your recipe after you have uploaded your package, you can make edits to it without updating the version (again, go via a PR).
You should ensure that the build number is bumped up one if doing this.
Owner
- Name: Arup
- Login: arup-group
- Kind: organization
- Email: media@arup.com
- Website: https://www.arup.com/
- Repositories: 168
- Profile: https://github.com/arup-group
We Shape a Better World
GitHub Events
Total
- Delete event: 1
- Push event: 1
- Pull request event: 2
- Create event: 1
Last Year
- Delete event: 1
- Push event: 1
- Pull request event: 2
- Create event: 1
Issues and Pull Requests
Last synced: over 1 year ago
All Time
- Total issues: 0
- Total pull requests: 7
- Average time to close issues: N/A
- Average time to close pull requests: about 1 hour
- Total issue authors: 0
- Total pull request authors: 2
- Average comments per issue: 0
- Average comments per pull request: 0.14
- Merged pull requests: 5
- Bot issues: 0
- Bot pull requests: 1
Past Year
- Issues: 0
- Pull requests: 2
- Average time to close issues: N/A
- Average time to close pull requests: 23 minutes
- Issue authors: 0
- Pull request authors: 1
- Average comments per issue: 0
- Average comments per pull request: 0.0
- Merged pull requests: 2
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
- brynpickering (9)
- dependabot[bot] (1)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- actions/checkout v3 composite
- tj-actions/changed-files v39 composite