We should probably provide a Docker image for running the tool. That would make it a lot easier to set up (no messing around with the SDK etc.). Basically, you can run a Docker container such that stuff inside the container has access to the Docker instance running outside of the container. Let's discuss on a video call.
The example in the tutorial is a bit artificial since the package is on PyPI, so we could also build a recipe for it with conda skeleton pypi.
Users shouldn't install the dependencies by recreating your exact environment (no conda env create -f environment.yml). That environment is for testing :-) The dependencies should be specified (without specific version number, unless necessary) here <https://github.com/Hogfeldt/bioconda_recipe_gen/blob/master/setup.py#L8>. It seems that the only dependencies are bioconda-utils docker-py gitdb2=2.0.5. This means that they'll be installed when the user runs python setup.py install or pip install ., which is what we want.
README says: "You should have a clone of the bioconda-recipes repo." This is not really a requirement for using the tool, is it?
Same as above, but in
docs/usage/installation
.Under "Mac specific", should link directly to section about SDK: https://docs.conda.io/projects/conda-build/en/latest/resources/compiler-tools.html#macos-sdk
docs/usage/installation
does not mention the SDK, is it not required there?In https://github.com/Hogfeldt/bioconda_recipe_gen/blob/master/docs/usage/tutorial.rst it says "Here is the final recipe for airr:" and then nothing is shown.
We should probably provide a Docker image for running the tool. That would make it a lot easier to set up (no messing around with the SDK etc.). Basically, you can run a Docker container such that stuff inside the container has access to the Docker instance running outside of the container. Let's discuss on a video call.
The example in the tutorial is a bit artificial since the package is on PyPI, so we could also build a recipe for it with
conda skeleton pypi
.Users shouldn't install the dependencies by recreating your exact environment (no
conda env create -f environment.yml
). That environment is for testing :-) The dependencies should be specified (without specific version number, unless necessary)here <https://github.com/Hogfeldt/bioconda_recipe_gen/blob/master/setup.py#L8>
. It seems that the only dependencies arebioconda-utils docker-py gitdb2=2.0.5
. This means that they'll be installed when the user runspython setup.py install
orpip install .
, which is what we want.