Eric Dill

@Tigeraus that's a good idea. My hesitation here is that repodata.json **is** the location where the md5 values are stored for local packages. I'd like to avoid inventing another place...

Thanks for the ping @jakirkham . I recently switched teams at work and so have not been paying enough attention to conda-forge, conda, conda-build and constructor as I should have...

mambaforge fails after the installation step with this same error if i have any env vars in my pkgs_dirs in conda config: ``` pkgs_dirs - $HOME/pkgs ``` mambaforge error ```...

oh awesome thanks for the feedback. i'll try that ~. another slight difference i noticed between conda/mamba and micromamba. Given these two condarc's that conda config --show-sources finds: ``` #...

@jonashaag whatever is shipped with the most recent release of mambaforge

can confirm: ~/pkgs works where $HOME/pkgs did not. thanks so much

oooo my sloppy bash comes home to roost! I'm usually so paranoid about adding the braces to my bash scripts 🤕 i can confirm that ${HOME} works

Thanks @minrk that's really helpful. I made updates based on your review. I only had one additional clarification question that I left on the in-line conversation [here](https://github.com/jupyterhub/jupyterhub/pull/2641#discussion_r303944990).

Thanks for all the feedback @willingc I'll be able to respond to it tomorrow

Thanks so much for the feedback @willingc . I've updated based on your comments, though I've got a few questions in return 😁